# CVE-2023-42793: JetBrains TeamCity Authentication Bypass

> Attackers can bypass authentication to execute arbitrary code on the TeamCity server, requiring immediate upgrade.

- **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 4 Oct 2023 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-w796-2gq9-7jm8

## What is CVE-2023-42793?

CVE-2023-42793 is a critical authentication bypass vulnerability in Jetbrains Teamcity, published on 19 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server was possible

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2023-42793?

It affects 1 product.


Products: Jetbrains Teamcity.

## How do I fix CVE-2023-42793?

No fix has been published for CVE-2023-42793 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 25 Oct 2023.

## Is CVE-2023-42793 being exploited?

Yes. Attackers have exploited CVE-2023-42793 in the wild since at least 4 Oct 2023, including in ransomware campaigns.

Public exploit code:

- JetBrains TeamCity Authentication Bypass CVE-2023-42793 Exploit (github_poc): https://github.com/H454NSec/CVE-2023-42793
- JetBrains TeamCity 2023.05.3 - Remote Code Execution (RCE), CVE-2023-42793 (github_poc): https://github.com/B4l3rI0n/CVE-2023-42793
- PoC of CVE-2023-42793 (github_poc): https://github.com/Zenmovie/CVE-2023-42793
- JetBrains TeamCity Unauthenticated Remote Code Execution - Python3 POC (github_poc): https://github.com/hotplugin0x01/CVE-2023-42793
- TeamCity CVE-2023-42793 exploit written in Rust (github_poc): https://github.com/junnythemarksman/CVE-2023-42793
- TeamCity RCE for Linux (CVE-2023-42793) (github_poc): https://github.com/hhesenjan/CVE-2023-42793

## 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-2024-27198](https://insights.sbomify.com/CVE-2024-27198/): 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-2023-42793 and fix it if it is affected.

What it is: CVE-2023-42793 is a critical authentication bypass vulnerability in Jetbrains Teamcity, published on 19 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-42793 in the wild since at least 4 Oct 2023, 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-2023-42793/ (Markdown: https://insights.sbomify.com/CVE-2023-42793/index.md)
```

## Sources

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

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