Skip to main content
VulnerabilityPublished

CVE-2026-133016: JetBrains TeamCity · Untrusted Functionality Inclusion

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:04 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 affected JetBrains TeamCity installations to version 2026.2.1 or 2026.1.5 or later. These versions contain the official fixes for this vulnerability. No other mitigation or workaround is indicated by the vendor advisory.

Description

A high-severity remote code execution vulnerability (CVE-2026-133016) exists in JetBrains TeamCity versions before 2026.2.1 and 2026.1.5. The flaw involves inclusion of functionality from an untrusted control sphere via script definitions in the Kotlin DSL settings repository. This allows an attacker with limited privileges to execute arbitrary code remotely. The vulnerability has been fixed in versions 2026.2.1 and 2026.1.5.

References

Community reviews

Loading reviews…