# CVE-2026-5802: idachev mcp-javadc HTTP os command injection

> Remote attackers can execute arbitrary OS commands via the jarFilePath argument in the mcp-javadc HTTP interface.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-r8rp-hx65-58jj

## What is CVE-2026-5802?

CVE-2026-5802 is a medium-severity command injection vulnerability in idachev mcp-javadc, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in idachev mcp-javadc up to 1.2.4. Impacted is an unknown function of the component HTTP Interface. Such manipulation of the argument jarFilePath leads to os command injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-5802 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5802 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5802 is a medium-severity command injection vulnerability in idachev mcp-javadc, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5802 exists.

Affected product: idachev mcp-javadc. 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-5802/ (Markdown: https://insights.sbomify.com/CVE-2026-5802/index.md)
```

## Sources

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

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