Skip to content
Fencer Intel
high 7.8

CVE-2026-111091 json

In JetBrains Junie CLI before 26.8.3 code execution was possible via an untrusted project's MCP server configuration

published 25d ago modified 25d ago also EUVD-2026-102144

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

In JetBrains Junie CLI before 26.8.3 code execution was possible via an untrusted project's MCP server configuration

Patch / fix

  • JetBrains Junie CLI 26.8.3

Is CVE-2026-111091 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
25d ago

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • JetBrains Junie CLI

Classification

Weakness
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.