# CVE-2026-49379: JetBrains TeamCity credential exposure in thread names

Source: https://junglewise.ai/threats/cve-2026-49379-jetbrains-teamcity-credential-exposure-in-thread-names  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-29. Updated: 2026-05-29  
License: CC BY 4.0 with a link back

CVE-2026-49379 · Severity: medium · CVSS 6.5 · Published 2026-05-29

JetBrains TeamCity, a platform used by software teams to automate building and testing code, was found to leak sensitive credentials in system thread names. An authenticated user could potentially view these thread names through monitoring tools or logs, leading to the exposure of passwords or access tokens. This could allow an attacker to gain unauthorized access to other integrated systems or sensitive project data.

Technologies: [Jetbrains TeamCity](https://junglewise.ai/threats/technologies/teamcity). Vendors: [Jetbrains](https://junglewise.ai/threats/vendors/jetbrains).

## Quick answers

**Is CVE-2026-49379 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-49379 being exploited in the wild.

**How severe is CVE-2026-49379?** Medium severity, with a CVSS score of 6.5, published 29 May 2026.

**Which products and versions are affected?** Jetbrains TeamCity before 2026.1.

**Is there a fix for CVE-2026-49379?** A patch was published on 2026-05-29: Fixed in version 2026.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-49379 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-49379?** Check whether you run Jetbrains TeamCity at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A vulnerability in JetBrains TeamCity (classified as CWE-522: Insufficiently Protected Credentials) allowed sensitive credentials to be exposed within the names of execution threads. This issue affects versions prior to 2026.1. An attacker with low-privileged network access could potentially observe these credentials by inspecting thread dumps, system logs, or monitoring interfaces where thread names are visible. The vulnerability has a CVSS score of 6.5, reflecting high confidentiality impact but requiring at least basic user authentication. JetBrains has addressed this issue in version 2026.1.

## Affected products

- JetBrains TeamCity before 2026.1

## Timeline

- 2026-05-29: advisory: CVE-2026-49379 published by JetBrains
- 2026-05-29: patched: Fixed in version 2026.1

## References

- [https://www.jetbrains.com/privacy-security/issues-fixed/](https://www.jetbrains.com/privacy-security/issues-fixed/)

## Related threats

- [JetBrains TeamCity stored XSS in classic build log](https://junglewise.ai/threats/cve-2026-111096-in-jetbrains-teamcity-before-2026-2-2026-1-4-2025-11-8-stored)
- [JetBrains TeamCity stored XSS in project overview](https://junglewise.ai/threats/cve-2026-111095-in-jetbrains-teamcity-before-2026-2-2026-1-4-2025-11-8-stored)
- [JetBrains TeamCity remote code execution in build messages protocol](https://junglewise.ai/threats/cve-2026-111094-in-jetbrains-teamcity-before-2026-2-2026-1-4-2025-11-8-remote)
- [JetBrains TeamCity Git submodule URL validation bypass](https://junglewise.ai/threats/cve-2026-106219-in-jetbrains-teamcity-before-2026-2-1-missing-validation-of-git)
- [JetBrains TeamCity Kotlin DSL sandbox escape RCE](https://junglewise.ai/threats/cve-2026-106218-in-jetbrains-teamcity-before-2026-1-3-2025-11-7-kotlin-dsl)