How severe is CVE-2026-106218?

CVE-2026-106218 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-106218 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (18th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-106218?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-106218 published?

CVE-2026-106218 was published on 2026-10-06 and last updated on 2026-10-07.

CVE-2026-106218

CVE-2026-106218 is a high-severity vulnerability with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-184.

Key facts

Severity: High (CVSS 3.x base score 8.8)
EPSS exploit prediction: 0% (18th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-184
Published: 2026-10-06
Last modified: 2026-10-07

Description

In JetBrains TeamCity before 2026.1.3 2025.11.7 kotlin DSL sandbox escape leading to RCE on the server was possible

Frequently asked questions

What is CVE-2026-106218?: In JetBrains TeamCity before 2026.1.3 2025.11.7 kotlin DSL sandbox escape leading to RCE on the server was possible
How severe is CVE-2026-106218?: CVE-2026-106218 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-106218 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (18th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-106218?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-106218 published?: CVE-2026-106218 was published on 2026-10-06 and last updated on 2026-10-07.

References

https://www.jetbrains.com/privacy-security/issues-fixed/

Other CWE-184 vulnerabilities

CVE-2026-87985 — Critical (CVSS 10.0): An arbitrary code execution vulnerability in Mistral Vibe allows an attacker to bypass command permission checks using…
CVE-2026-79696 — Critical (CVSS 10.0): A Code Injection vulnerability in adk web in Google Cloud Agent Development Kit (ADK) for Python versions 2.0.0 through…
CVE-2026-57138 — Critical (CVSS 9.9): PraisonAI is a multi-agent teams system. From 1.4.0 until 1.7.2, codeMode in…
CVE-2026-65083 — Critical (CVSS 9.9): NVIDIA OpenShell for Linux contains a vulnerability in its sandbox provisioning API, where an attacker could cause an…
CVE-2026-47392 — Critical (CVSS 9.9): PraisonAI is a multi-agent teams system. Prior to version 4.6.40 of PraisonAI, corresponding to version 1.6.40 of…
CVE-2026-28363 — Critical (CVSS 9.9): In OpenClaw before 2026.2.23, tools.exec.safeBins validation for sort could be bypassed via GNU long-option…

Browse all CWE-184 vulnerabilities →