Skip to content

AAK-MCP-JUNIE-CVE-2026-111091-001: JetBrains Junie CLI before 26.8.3 (npm build below 2548.5.0): an untrusted project's MCP server configuration runs code

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
JunieCliUntrustedProjectMcpConfig

What it detects

Junie CLI is JetBrains' coding agent for the terminal, published on npm as @jetbrains/junie and earlier as @jetbrains/junie-cli. It reads MCP servers from the project's .junie/mcp/mcp.json as well as from the user's own configuration. Before 26.8.3, an untrusted project's MCP server configuration could run code on the machine of a user who started Junie in it (CVE-2026-111091, CVSS 3.1 7.8, CWE-829). The npm package is a launcher that installs the Junie build named in its junieVersion field, and its version is that build number: 26.8.3 is build 2548.5, published to npm as 2548.5.0 on 2026-08-03. Checked in the builds: 888.112, the oldest @jetbrains/junie release, and 2470.4, the last npm release before the fix, read the project's .junie/mcp/mcp.json, and 2548.5 adds a trust prompt that previews the project's MCP servers.

How to fix

Upgrade @jetbrains/junie to 2548.5.0 (Junie 26.8.3) or later and pin it. @jetbrains/junie-cli stopped at 1468.30.0, so move to @jetbrains/junie. Until then, do not start Junie in a repository you do not trust, and read its .junie/mcp/mcp.json first.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-JUNIE-CVE-2026-111091-001

Limitations

Reports @jetbrains/junie and @jetbrains/junie-cli from 888.0.0 up to 2548.5.0 where a project states the version in a package.json or lockfile entry. An unpinned reference resolves to the newest release and is not reported. Junie is usually installed globally, by its install script, Homebrew or npm install -g, which no file AAK reads. The launcher installs one build, and Junie's shim can fetch and run another (--use-version, or a channel's latest build), so a stated version does not prove which build runs. @jetbrains/junie-cli releases below 888.0.0, which install the EAP builds of August 2025 to February 2026, and its empty 1.0.0 are not reported. A project's own .junie/mcp/mcp.json is not read. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-JUNIE-CVE-2026-111091-001.md: the page then shows that text, with the registry reference appended under it.