CVE-2025-68166
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 a DOM-based XSS was possible on the OAuth connections tab
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 confidenceA DOM-based cross-site scripting (XSS) vulnerability exists in JetBrains TeamCity versions prior to 2025.11. The vulnerability is located in the OAuth connections tab where malicious JavaScript code can be injected into the DOM through insufficient input sanitization. This allows an attacker to execute arbitrary scripts in the context of a user's browser session.
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 versionAccess the TeamCity administration interface and navigate to the 'About' or 'Server Administration' section to view the exact version number. Alternatively, check the version from the server's installation logs or startup output.Affected if The installed version is any release prior to 2025.11 (for example, 2024.x, 2023.x, or earlier).
-
Verify OAuth connections feature existsNavigate to the TeamCity administration area and locate the OAuth connections or OAuth settings tab within the server configuration or user authentication settings.Affected if The OAuth connections functionality is present and accessible in the TeamCity interface, regardless of whether it is actively configured with providers.
-
Confirm input handling in OAuth connection fieldsReview the HTML source or DOM inspection of the OAuth connection configuration page. Examine the input fields where OAuth provider names, client IDs, or other connection parameters are entered.Affected if Input fields in the OAuth connections tab accept and render special characters without visible sanitization or encoding in the page source.
A TeamCity installation is affected if it runs any version prior to 2025.11 and has the OAuth connections feature accessible, since the lack of input sanitization in that feature allows script injection.
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 to obtain the patch. Until then, restrict access to the OAuth connections functionality to trusted users only.
TeamCity 2025.11
- Back up your TeamCity server data, configuration, and database before starting the upgrade
- Download TeamCity 2025.11 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- Stop the TeamCity server service
- Follow the official TeamCity upgrade instructions to install the new version
- Start the TeamCity server and verify the upgrade was successful
- Navigate to the OAuth connections tab and verify the XSS vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68166 — 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-68166 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