Skip to main content
VulnerabilityPublished

CVE-2026-133015: JetBrains TeamCity · Incorrect Privilege Assignment

Affects JetBrains TeamCitySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2026.2.1 or 2026.1.5 soon.

Data as of 19 Nov 2026, 12:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (JetBrains)CVSS 3.18.8
Patch
Available – fixed in 2026.2.1, 2026.1.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade JetBrains TeamCity to 2026.2.1 or 2026.1.5.

Affected software

ProductAffectedFixed in
JetBrainsTeamCityAffected
  • >=2026.2 <2026.2.1
Fixed in
  • 2026.2.1
JetBrainsTeamCityAffected
  • <2026.1.5
Fixed in
  • 2026.1.5

AI-suggested

Upgrade JetBrains TeamCity to version 2026.2.1 or 2026.1.5 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated by the vendor advisory.

Description

CVE-2026-133015 is a high-severity vulnerability in JetBrains TeamCity that allows remote code execution due to incorrect privilege assignment in the Kotlin DSL sandbox. This flaw affects TeamCity versions prior to 2026.2.1 and 2026.1.5. The vulnerability arises from improper handling of boot classpath libraries, enabling attackers with limited privileges to execute arbitrary code remotely. JetBrains has fixed this issue in versions 2026.2.1 and 2026.1.5.

References

Community reviews

Loading reviews…