JetBrains Junie code execution via terminal environment in project files
- Exploited
- No known exploitation
- Fix
- Fixed in 253.819.35, 252.819.35
- Who is exposed
- Not reported
Summary
In JetBrains Junie, an attacker who can get a user to open a crafted project can run code on that user's machine through terminal environment settings stored in project files. The attack requires local access and some action by the user, and it needs no login.
Written by a model
Original description
In JetBrains Junie before 252.819.35, 253.819.35 code execution was possible via terminal environment settings in project files
What to do
Upgrade to a fixed version: 253.819.35, 252.819.35.
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-133198 (In JetBrains Junie before 252.819.35, 253.819.35 code execution was possible via terminal environment settings in project files), 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-133198 (entry last updated 2026-11-19):
Affected:
- JetBrains Junie: from 253, fixed in 253.819.35; fixed in 252.819.35
Fixed versions: 253.819.35, 252.819.35.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133198 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133198 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-133198
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-133198"}.Affected versions
- JetBrains JunieFrom 253 · fixed in 253.819.35; fixed in 252.819.35
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 7.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- 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-133198 |
| Record | NVD · CVE-2026-133198 |
Questions about CVE-2026-133198
Is CVE-2026-133198 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-133198?
Junie: from 253 before 253.819.35; before 252.819.35.
Source: cve.now feed data
How do I fix CVE-2026-133198?
Upgrade to a fixed version: 253.819.35, 252.819.35.
Source: cve.now feed data
Related
- CVE-2025-59458In JetBrains Junie before 252.284.66, 251.284.66, 243.284.66, 252.284.61, 251.284.61, 243.284.61, 252.284.50, 252.284.54, 251.284.54…
- CVE-2026-111091In JetBrains Junie CLI before 26.8.3 code execution was possible via an untrusted project's MCP server configuration
- CVE-2026-133195In JetBrains Junie CLI before 26.6.29 files outside the project directory could be modified by agent file tools
- CVE-2026-123852In JetBrains Junie GitHub Action before 1.8.0 code execution with workflow credentials was possible via fork updates
- CVE-2026-123315In JetBrains Junie CLI before 26.8.24 command execution was possible via the Allow Similar Commands option
- CVE-2026-117530In JetBrains Junie CLI before 26.8.17 command execution was possible due to incomplete validation of allowlisted commands
No corrections so far. Something wrong on this page? Report an error.