# CVE-2024-27198: JetBrains TeamCity Authentication Bypass

> Attackers can bypass authentication to perform admin actions in JetBrains TeamCity, requiring an upgrade to secure the CI/CD pipeline.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 7 Mar 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-xh94-49wq-7h2h

## What is CVE-2024-27198?

CVE-2024-27198 is a critical authentication bypass vulnerability in Jetbrains Teamcity, published on 4 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In JetBrains TeamCity before 2023.11.4 authentication bypass allowing to perform admin actions was possible

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2024-27198?

It affects 1 product.


Products: Jetbrains Teamcity.

## How do I fix CVE-2024-27198?

No fix has been published for CVE-2024-27198 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 28 Mar 2024.

## Is CVE-2024-27198 being exploited?

Yes. Attackers have exploited CVE-2024-27198 in the wild since at least 7 Mar 2024, including in ransomware campaigns.

Public exploit code:

- CVE-2024-27198 & CVE-2024-27199 Authentication Bypass --> RCE in JetBrains TeamCity Pre-2023.11.4 (github_poc): https://github.com/W01fh4cker/CVE-2024-27198-RCE
- Exploit for CVE-2024-27198 - TeamCity Server (github_poc): https://github.com/yoryio/CVE-2024-27198
- CVE-2024-27198 & CVE-2024-27199 PoC - RCE, Admin Account Creation, Enum Users, Server Information (github_poc): https://github.com/Stuub/RCity-CVE-2024-27198
- Proof of Concept for Authentication Bypass in JetBrains TeamCity Pre-2023.11.4 (github_poc): https://github.com/Chocapikk/CVE-2024-27198
- https://github.com/passwa11/CVE-2024-27198-RCE (github_poc): https://github.com/passwa11/CVE-2024-27198-RCE
- is a PoC tool that targets a vulnerability in the TeamCity server (CVE-2024-27198) (github_poc): https://github.com/geniuszly/CVE-2024-27198

## Other vulnerabilities in Jetbrains Teamcity

- [CVE-2026-63077](https://insights.sbomify.com/CVE-2026-63077/): JetBrains TeamCity Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2023-42793](https://insights.sbomify.com/CVE-2023-42793/): JetBrains TeamCity Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-27199](https://insights.sbomify.com/CVE-2024-27199/): JetBrains TeamCity Relative Path Traversal (high 7.3, exploited in the wild)
- [CVE-2024-23917](https://insights.sbomify.com/CVE-2024-23917/): Auth bypass in TeamCity (critical 9.8)
- [CVE-2022-24331](https://insights.sbomify.com/CVE-2022-24331/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27198 and fix it if it is affected.

What it is: CVE-2024-27198 is a critical authentication bypass vulnerability in Jetbrains Teamcity, published on 4 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-27198 in the wild since at least 7 Mar 2024, including in ransomware campaigns.

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-2024-27198/ (Markdown: https://insights.sbomify.com/CVE-2024-27198/index.md)
```

## Sources

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

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