CVE-2025-68165
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 reflected XSS was possible on VCS Root setup
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 confidenceReflected XSS vulnerability in JetBrains TeamCity's VCS Root setup allows attackers to inject malicious scripts via crafted URLs, affecting versions before 2025.11.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 versionLog into the TeamCity web interface as an administrator, then navigate to the 'Administration' > 'Server Administration' > 'Server Information' page. The version number is displayed there.Affected if The displayed version is any version number lower than 2025.11 (for example, 2025.10, 2024.2, etc.)
-
Confirm VCS Root feature is accessibleIn the TeamCity web interface, navigate to 'Project Settings' > 'VCS Roots'. This feature is a core component of TeamCity and is typically available in all installations.Affected if The VCS Root configuration page loads successfully, indicating the vulnerable feature is present in the environment
-
Verify web interface is reachableAttempt to access the TeamCity web console URL (typically on port 80 or 443). The reflected XSS is triggered through crafted URLs to the VCS Root setup endpoint.Affected if The TeamCity web interface is accessible over HTTP/HTTPS, as this is required for the URL-based reflected XSS attack vector
If your TeamCity server version is below 2025.11 and the web interface is accessible, you are affected by this reflected XSS vulnerability in the VCS Root setup feature.
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 TeamCity to version 2025.11 or later which contains the security patch for this reflected XSS vulnerability.
2025.11
- 1. Back up your TeamCity data directory and database before upgrading
- 2. Download TeamCity version 2025.11 or later from the official JetBrains website
- 3. Stop the TeamCity server
- 4. Install the new version following the official TeamCity upgrade documentation
- 5. Start the TeamCity server and verify the upgrade was successful
- 6. Verify the VCS Root setup functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68165 — 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-68165 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