Skip to main content
Menu
CVEs

JetBrains TeamCity code injection in Kotlin DSL from matrix build parameters

CVE-2026-133026EUVD-2026-129799GHSA-8WRH-G8WR-V7RQPublished November 19, 2026, updated

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.2.1, 2026.1.5
Who is exposed
Not reported

Summary

JetBrains TeamCity has a code injection flaw in the Kotlin DSL it generates from matrix build parameters, which lets an attacker inject code into that generated DSL. An attacker can reach it remotely over the network, but only after logging in with high privileges.

Written by a model

Original description

In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build parameters

What to do

Upgrade to a fixed version: 2026.2.1, 2026.1.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133026 (In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build parameters), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133026 (entry last updated 2026-11-20):
Affected:
- JetBrains TeamCity: from 2026.2, fixed in 2026.2.1; fixed in 2026.1.5
Fixed versions: 2026.2.1, 2026.1.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133026 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133026 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.jetbrains.com/privacy-security/issues-fixed/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133026
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133026"}.

Affected versions

cve.now Index

11Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.2/10CVSS 7.2, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  2. CVE published
  3. First seen by cve.now1 day
  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkjetbrains.com · privacy-security/issues-fixed
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133026
RecordNVD · CVE-2026-133026

Questions about CVE-2026-133026

Is CVE-2026-133026 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133026?

TeamCity: from 2026.2 before 2026.2.1; before 2026.1.5.

Source: cve.now feed data

How do I fix CVE-2026-133026?

Upgrade to a fixed version: 2026.2.1, 2026.1.5.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.