Skip to content
The Injection_
LIVE
LIVElast sweep next in--:--:--

[ RSS ][ JSON ][ llms.txt ]

Junie CLI: agent file tools could write outside the project

JetBrains fixed a path confinement flaw that let Junie CLI's agent file tools change files outside the project directory.

· JetBrains · Research by JetBrains security team

CVE-2026-133195
HIGHVulnerability

CVE-2026-133195 let the agent file tools in JetBrains Junie CLI modify files outside the project directory. JetBrains published the flaw on November 19, 2026, scored it 7.5 on CVSS 3.1 and fixed it in Junie CLI 26.6.29.

01What happened

JetBrains published CVE-2026-133195 on November 19, 2026, acting as the CVE Numbering Authority for its own products. The record states that in Junie CLI before 26.6.29, files outside the project directory could be modified by agent file tools. JetBrains scored the flaw 7.5 on CVSS 3.1 and shipped the fix in Junie CLI 26.6.29.

02How it works

File tools are what a coding agent uses to read and write source files, and Junie CLI did not hold their targets inside the project it was working on. JetBrains classifies the flaw as CWE-73, external control of file name or path, which is the pattern where something outside the program decides which path it touches. The record publishes no proof of concept, so the vector JetBrains assigned is the only description of the path.

03Who is affected

Every Junie CLI release below 26.6.29 is listed as affected, and 26.6.29 and later carry a default status of unaffected. JetBrains names no other product in the record. The published vector needs one user action and no privileges, which fits a developer running the agent on content that came from somewhere else.

04What to do

Update Junie CLI to 26.6.29 or later, which is the only remedy the record gives. Until that update lands, run Junie CLI only on projects and inputs you control, and do not rely on the project directory to bound what the agent writes.

Questions people ask

Which Junie CLI version fixes CVE-2026-133195?
JetBrains Junie CLI 26.6.29 fixes CVE-2026-133195. The CVE record JetBrains published on November 19, 2026 marks every version below 26.6.29 as affected and sets a default status of unaffected for the rest. No workaround appears in the record, so installing the updated CLI is the only remedy JetBrains names for this flaw.
What can an attacker do with CVE-2026-133195?
CVE-2026-133195 lets the agent file tools in Junie CLI modify files outside the project directory, according to the description JetBrains filed. JetBrains rates the confidentiality, integrity and availability impact all high, giving a CVSS 3.1 base score of 7.5. The record stops there and includes no proof of concept, so the concrete attack path is not public.
Does exploiting CVE-2026-133195 need the developer to do something?
Exploitation of CVE-2026-133195 requires one user action, per the vector JetBrains published: AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H. The path is reachable over the network and needs no privileges, but attack complexity is rated high and user interaction is required. That combination fits a developer pointing the Junie CLI agent at content supplied from outside.
Is CVE-2026-133195 being exploited?
No exploitation of CVE-2026-133195 has been recorded. The CISA Vulnrichment data attached to the CVE record on November 19, 2026 sets exploitation to none and automatable to no, while rating the technical impact total. Those values describe the state when the record was enriched and can change later, so defenders should update Junie CLI rather than wait.

Sources 3 links, all fetched

  1. 1github.comGitHub Advisory
  2. 2cveawg.mitre.orgCVE Record
  3. 3jetbrains.comJetBrains Fixed Issues