JetBrains TeamCity command injection in project import artifact copy scripts
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.2.2, 2026.1.6
- Who is exposed
- Not reported
Summary
In JetBrains TeamCity before 2026.2.2, 2026.1.6 command injection in Project Import artifact copy scripts was possible
What to do
Upgrade to a fixed version: 2026.2.2, 2026.1.6.
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-133100 (In JetBrains TeamCity before 2026.2.2, 2026.1.6 command injection in Project Import artifact copy scripts was possible), 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-133100 (entry last updated 2026-11-20):
Affected:
- JetBrains TeamCity: from 2026.2, fixed in 2026.2.2; fixed in 2026.1.6
Fixed versions: 2026.2.2, 2026.1.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133100 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133100 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-133100
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-133100"}.Affected versions
- JetBrains TeamCityFrom 2026.2 · fixed in 2026.2.2; fixed in 2026.1.6
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.8/10CVSS 6.8, 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
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jetbrains.com · privacy-security/issues-fixed |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133100 |
| Record | NVD · CVE-2026-133100 |
Questions about CVE-2026-133100
Is CVE-2026-133100 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-133100?
TeamCity: from 2026.2 before 2026.2.2; before 2026.1.6.
Source: cve.now feed data
How do I fix CVE-2026-133100?
Upgrade to a fixed version: 2026.2.2, 2026.1.6.
Source: cve.now feed data
Related
- CVE-2026-133092In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git submodule URLs
- CVE-2026-133095In JetBrains TeamCity before 2026.2.2, 2026.1.6 a CSRF attack was possible on the Hub integration settings
- CVE-2026-133089In JetBrains TeamCity before 2026.2.2, 2026.1.6 the TFS helper process exposed an unauthenticated command server
- CVE-2026-133091In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possible
- CVE-2026-133094In JetBrains TeamCity before 2026.2.2 missing authorization allowed project developers to read arbitrary HashiCorp Vault secrets
- CVE-2026-133097In JetBrains TeamCity before 2026.2.2, 2026.1.6 agent Push authorization keys were predictable
No corrections so far. Something wrong on this page? Report an error.