CVE-2026-49372
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, 2025.11.5 unauthenticated SSRF via build status was possible
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 · high confidenceAn unauthenticated Server-Side Request Forgery (SSRF) vulnerability in JetBrains TeamCity's build status feature allows remote attackers to induce the TeamCity server to make arbitrary HTTP requests to internal or external resources by manipulating build status parameters.
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< 2025.11.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 versionNavigate to Administration > About in the TeamCity web UI, or check the teamcity-server.log file for version information at <TeamCity data directory>/logs/teamcity-server.logAffected if The installed version is lower than 2025.11.5 (versions prior to 2025.11.5 are affected)
-
Verify build status feature accessibilityAttempt to access the build status endpoint without authentication: http://<teamcity-server>/buildStatus/ for example, or check if /app/rest/builds/.. endpoints accept requests without authenticationAffected if The build status endpoints are accessible without authentication (this is required for the SSRF to be exploitable)
-
Confirm external network exposureCheck if the TeamCity web interface is exposed to the internet or untrusted networks. Review firewall rules, reverse proxy configuration, or cloud security group settings that allow external access to TeamCity ports (usually 80/443)Affected if TeamCity is reachable from untrusted network segments or the internet without authentication barriers
A user is affected if their TeamCity version is below 2025.11.5 AND the build status feature is accessible to unauthenticated users on a network they do not fully control.
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 · scoped2025.11.5
Upgrade TeamCity to version 2026.1 or 2025.11.5 or later to patch the SSRF vulnerability.
2025.11.5
- 1. Back up your existing TeamCity installation and database before proceeding with the upgrade
- 2. Download TeamCity 2025.11.5 (or latest 2026.x release) from the official JetBrains website: https://www.jetbrains.com/teamcity/download/
- 3. Stop the TeamCity server and all running builds
- 4. Install the new version following the standard TeamCity upgrade procedure
- 5. Start the TeamCity server and verify all services are running correctly
- 6. Test that build status functionality works properly
- 7. Verify the SSRF vulnerability is no longer present by confirming the server no longer makes arbitrary requests to internal resources via build status endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49372 — 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-49372 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