CVE-2026-49375
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 reflected XSS was possible on the repository download page
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 confidenceReflected XSS vulnerability in JetBrains TeamCity's repository download page allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in the HTTP response and executes in victim browsers.
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
- 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.
-
Confirm TeamCity is installedCheck if TeamCity is running by accessing the web interface at your TeamCity server URL, or look for TeamCity processes running on common ports (8111 is default).Affected if TeamCity is not present on the system.
-
Identify TeamCity versionNavigate to the TeamCity web UI and click on 'Administration' > 'Server Administration' > 'Server Information', or append /admin/serverInfo.html to your TeamCity URL. The version number is displayed on that page.Affected if The installed version is < 2025.11.5.
-
Check if repository download feature is accessibleAttempt to access the repository download page. This is typically found at URLs like /repository/download or similar paths under your project/build configuration.Affected if The repository download functionality is enabled and accessible to users.
-
Verify server configurationCheck TeamCity's internal properties file (teamcity-server.properties) located in the TeamCity config directory for custom repository-related settings or plugins that may extend the download functionality.Affected if Custom plugins or configurations that extend the download functionality are installed.
You are affected if TeamCity is running with a version lower than 2025.11.5 and the repository download feature is accessible to 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.5
Upgrade to TeamCity 2026.1 or 2025.11.5 or later to obtain the XSS fix; as a temporary measure, avoid clicking untrusted links to the repository download page.
2025.11.5 or later (preferably the latest stable 2025.x or 2026.x release)
- 1. Check current TeamCity version by navigating to Administration > Diagnostics > About
- 2. Back up the TeamCity data directory (by default <TeamCity Data Directory>/config)
- 3. Download the latest TeamCity release from https://www.jetbrains.com/teamcity/download/
- 4. Stop the TeamCity server
- 5. Install the new version following the upgrade instructions in the official documentation
- 6. Start the TeamCity server and verify the upgrade was successful
- 7. Confirm the repository download page is accessible and the XSS vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49375 — 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-49375 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