# CVE-2026-111091: Code injection in Junie CLI

> Attackers can execute arbitrary code via malicious MCP server configurations in untrusted projects using JetBrains Junie CLI.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-44gv-r4c4-w64m

## What is CVE-2026-111091?

CVE-2026-111091 is a high-severity code injection vulnerability in JetBrains Junie CLI, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2026-111091?


## How do I fix CVE-2026-111091?

No fix has been published for CVE-2026-111091 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111091 being exploited?

There is no known exploitation of CVE-2026-111091 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111091 and fix it if it is affected.

What it is: CVE-2026-111091 is a high-severity code injection vulnerability in JetBrains Junie CLI, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-111091 in the wild and no public exploit code.

Affected product: JetBrains Junie CLI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111091/ (Markdown: https://insights.sbomify.com/CVE-2026-111091/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111091
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111091
- OSV: https://osv.dev/vulnerability/CVE-2026-111091

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111091/
Summaries are generated and may contain mistakes; the official description above is the record.