CVE detail
CVE-2026-49379
In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names
Buzz score
Why this CVE is surfacing
This all-time snapshot uses the same composite formula as Trending across a 30-year evidence window, rather than a current rolling window.
Buzz score components · mention 6.9 · diversity 5.0 · KEV 0.0 · OTX 0.0 · PoC 0.0
Why it matters now
Mention timeline
- Total mentions
- 0
- within the 30d window
- Peak daily
- 0
- highest bucket
Evidence
Source links by recency
1 source links · newest first
- https://www.jetbrains.com/privacy-security/issues-fixed/www.jetbrains.com
No excerpt available.
Vendor Advisorywww.jetbrains.comMay 29, 2026, 7:16 PM
Exploit code
Public exploit repository references
Public PoC repositories are third-party, potentially unsafe artifacts. Treat their code as untrusted and use it only on authorized systems in an isolated, least-privilege environment. cvebuzz does not execute the code or verify that an exploit works.
0 repository references · best confidence N/A · max 0 stars
Related records
Similar CVEs
6 related CVEs with shared weakness or product evidence
- CVE-2025-26492CVSS 7.7 · High
In JetBrains TeamCity before 2024.12.2 improper Kubernetes connection settings could expose sensitive resources
- CVE-2024-56354CVSS 5.5 · Medium
In JetBrains TeamCity before 2024.12 password field value were accessible to users with view settings permission
- CVE-2024-47161CVSS 4.3 · Medium
In JetBrains TeamCity before 2024.07.3 password could be exposed via Sonar runner REST API
- CVE-2024-39879CVSS 5.0 · Medium
In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings
- CVE-2024-39878CVSS 4.1 · Medium
In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection
- CVE-2020-7909CVSS 7.5 · High
In JetBrains TeamCity before 2019.1.5, some server-stored passwords could be shown via the web UI.