# CVE-2026-132893: In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an SSRF via pipeline repository branch listing was possible


- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-pcm6-552x-c59v

## What is CVE-2026-132893?

CVE-2026-132893 is a high-severity vulnerability in JetBrains TeamCity, published on 19 Nov 2026. 

### Official description

In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an SSRF via pipeline repository branch listing was possible

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-132893?


## How do I fix CVE-2026-132893?

Upgrade JetBrains TeamCity to the fixed version for your release line. The advisory names 2026.2, 2026.1.4 and 2025.11.8.

## Is CVE-2026-132893 being exploited?

There is no known exploitation of CVE-2026-132893 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132893 and fix it if it is affected.

What it is: CVE-2026-132893 is a high-severity vulnerability in JetBrains TeamCity, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132893 in the wild and no public exploit code.

Affected product: JetBrains TeamCity. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132893/ (Markdown: https://insights.sbomify.com/CVE-2026-132893/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132893
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132893
- OSV: https://osv.dev/vulnerability/CVE-2026-132893

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132893/
Summaries are generated and may contain mistakes; the official description above is the record.
