CVE-2026-28194
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.3 open redirect was possible in the React project creation flow
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 confidenceAn open redirect vulnerability existed in the React project creation flow of JetBrains TeamCity versions before 2025.11.3. The application failed to properly validate redirect URLs supplied during the project creation process, allowing attackers to craft malicious URLs that would redirect users to arbitrary external sites.
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.3CVSS 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 JetBrains TeamCity is installedAccess the TeamCity web interface or check for teamcity processes running on the serverAffected if TeamCity is present in the environment
-
Identify the installed TeamCity versionNavigate to the TeamCity Administration > Diagnostics > Version page, or check the buildServer.properties file for the version numberAffected if The installed version is lower than 2025.11.3 (e.g., 2025.10.x, 2024.x, or earlier)
-
Verify the React project creation feature is accessibleLog into TeamCity and attempt to access the project creation flow (Administration > Projects > Create Project)Affected if The project creation interface is available and functional
If TeamCity is present and the installed version is before 2025.11.3, the environment is vulnerable to the open redirect flaw in the project creation flow.
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.3
Upgrade JetBrains TeamCity to version 2025.11.3 or later. As a temporary measure, users should be cautious when clicking project creation links from untrusted sources.
2025.11.3
- 1. Identify current TeamCity version by navigating to Administration > Troubleshooting > Server Information
- 2. Review TeamCity upgrade documentation at https://www.jetbrains.com/help/teamcity/upgrade-instructions.html
- 3. Create a complete backup of the TeamCity data directory and database before upgrading
- 4. Download TeamCity 2025.11.3 from the official JetBrains website or your existing license download area
- 5. Stop the TeamCity server service
- 6. Install the new version following the standard upgrade procedure (run the installer and point to existing data directory)
- 7. Start the TeamCity server and verify the upgrade was successful
- 8. Confirm the vulnerability is resolved by attempting to access the React project creation flow with a malicious redirect URL
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28194 — 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-28194 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