JetBrains Junie GitHub Action OS command injection in action version input
- Exploited
- No known exploitation
- Fix
- Fixed in 1.10.0
- Who is exposed
- Not reported
Summary
JetBrains' Junie GitHub Action is affected by a command injection flaw in its action version input. An attacker can reach it remotely, without logging in, and run commands on the affected system.
Written by a model
Original description
In JetBrains Junie GitHub Action before 1.10.0 command injection was possible via the action version input
What to do
Upgrade to a fixed version: 1.10.0.
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-133194 (In JetBrains Junie GitHub Action before 1.10.0 command injection was possible via the action version input), 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-133194 (entry last updated 2026-11-19):
Affected:
- JetBrains Junie GitHub Action: fixed in 1.10.0
Fixed versions: 1.10.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133194 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133194 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-133194
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-133194"}.Affected versions
- JetBrains Junie GitHub Actionfixed in 1.10.0
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.6/10CVSS 5.6
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- 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-133194 |
| Record | NVD · CVE-2026-133194 |
Questions about CVE-2026-133194
Is CVE-2026-133194 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-133194?
Junie GitHub Action: before 1.10.0.
Source: cve.now feed data
How do I fix CVE-2026-133194?
Upgrade to a fixed version: 1.10.0.
Source: cve.now feed data
Related
- CVE-2026-123852In JetBrains Junie GitHub Action before 1.8.0 code execution with workflow credentials was possible via fork updates
- CVE-2026-133193In JetBrains Junie GitHub Action before 1.10.0 code execution was possible via path traversal in feedback session markers
- CVE-2026-123851In JetBrains Junie GitHub Action before 1.6.4 prompt injection protection could be bypassed via HTML-encoded characters
- CVE-2026-133192In JetBrains Junie GitHub Action before 1.10.0 untrusted fork code could be processed in privileged workflow runs
- CVE-2026-133254In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Code Provenance plugin
- CVE-2026-133253In JetBrains IntelliJ IDEA before 2026.3 untrusted projects could read files of other open projects via the built-in web server
No corrections so far. Something wrong on this page? Report an error.