CVE-2025-67741
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 2025.11 stored XSS was possible via session attribute
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in JetBrains TeamCity versions prior to 2025.11. The vulnerability allows attackers to inject malicious scripts through session attributes, which are then stored and executed when other users interact with the affected session data.
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.11CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 versionAccess the TeamCity administration UI and navigate to 'Administration' > 'Server Administration' > 'Server Information' to view the exact version number, or query the server directly via the API endpoint /app/rest/server/versionAffected if The displayed version is any version prior to 2025.11 (for example 2025.10, 2025.4, 2024.x, etc.)
-
Confirm version via command lineCheck the TeamCity version from the server console or logs: look in <TeamCity_home>/logs/teamcity-server.log for a line containing 'TeamCity version' or run 'teamcity-version.sh' or 'teamcity-version.bat' from the bin directoryAffected if The logged or printed version is < 2025.11
-
Verify session attribute handlingReview TeamCity configuration files (buildServer.properties or teamcity-startup.properties) for custom session attribute handling or custom plugins that process session dataAffected if Custom session attribute processing is in use and the TeamCity version is < 2025.11
You are affected if your installed TeamCity version is any release prior to 2025.11 and your instance processes session attributes that could be displayed to other users.
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
Upgrade JetBrains TeamCity to version 2025.11 or later. As a temporary workaround, implement strict input validation on session attribute handling and ensure proper output encoding when session attributes are displayed to users.
TeamCity 2025.11
- 1. Create a complete backup of the TeamCity data directory (typically <TeamCity Data Directory>)
- 2. Create a database backup of the TeamCity database
- 3. Review the TeamCity 2025.11 release notes for any known issues or migration requirements
- 4. Download TeamCity 2025.11 from the official JetBrains website (www.jetbrains.com)
- 5. Stop the TeamCity server gracefully
- 6. Install the TeamCity 2025.11 upgrade following standard upgrade procedures
- 7. Start the TeamCity server
- 8. Verify the server is operational and check that the XSS vulnerability in session attribute handling is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67741 — 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-2025-67741 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