CVE-2026-49379
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn JetBrains TeamCity before 2026.1 credentials could be exposed in thread names
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn JetBrains TeamCity versions prior to 2026.1, sensitive credentials were being included in thread names, potentially exposing authentication secrets through thread dumps, logs, or monitoring tools that access thread information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed TeamCity versionCheck the TeamCity admin interface under Administration > Server Configuration, or locate the teamcity-version.txt file in the TeamCity data directory, or review buildServer.propertiesAffected if The version is any release prior to 2026.1
-
Review thread dumps for credential exposureObtain a thread dump through the TeamCity admin UI diagnostics, JMX console, or OS diagnostic tools. Search within the thread names for patterns resembling authentication tokens, API keys, session IDs, or user credentialsAffected if Thread names contain authentication credentials, tokens, or sensitive session identifiers
-
Search server logs for credential patterns in thread namesSearch TeamCity server logs (in the logs directory) for thread names that include authentication material such as 'token', 'auth', 'session', 'bearer', or credential-like stringsAffected if Log entries display thread names with embedded credentials or tokens
-
Audit monitoring and observability toolsReview any external monitoring systems, APM tools, or log aggregation platforms that expose thread names. Search their outputs for thread names that may contain authentication informationAffected if Monitoring outputs, dashboards, or trace data show thread names with exposed credentials
If running any TeamCity version below 2026.1 and thread dumps, logs, or monitoring outputs contain thread names with authentication credentials, the environment is affected by this vulnerability
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.1
Upgrade TeamCity to version 2026.1 or later. If immediate upgrade is not possible, implement monitoring to detect credential patterns in thread names and restrict access to thread information.
TeamCity 2026.1
- Backup your TeamCity installation and all data before upgrading
- Review the TeamCity 2026.1 release notes for any specific upgrade requirements or changes
- Upgrade your TeamCity installation to version 2026.1
- After upgrade, verify that credentials are no longer exposed in thread names by reviewing thread dumps or logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49379 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data