Quick answers
- Is CVE-2026-106218 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106218 being exploited in the wild.
- How severe is CVE-2026-106218?
- High severity, with a CVSS score of 8.8, published 6 October 2026.
- Which products and versions are affected?
- Jetbrains TeamCity before 2026.1.3, 2025.11.7.
- Is there a fix for CVE-2026-106218?
- Yes: fixed in TeamCity 2026.1.3, 2025.11.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106218 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-106218?
- Check whether you run Jetbrains TeamCity at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: TeamCity 2026.1.3, 2025.11.7
Technical details
A sandbox escape in TeamCity's Kotlin DSL sandbox allows remote code execution on the server through improper isolation of Kotlin DSL evaluation. The vulnerability requires network access to the TeamCity instance but does not require prior authentication. Successful exploitation grants an attacker arbitrary code execution in the context of the TeamCity server process.
Affected products
- JetBrains TeamCity before 2026.1.3, 2025.11.7
Timeline
- 2026-10-06: disclosed