# CVE-2026-7812: 54yyyu code-mcp MCP Tool server.py git_operation command injection

> Remote attackers can execute arbitrary commands via the git_operation function in the code-mcp MCP Tool due to improper input validation.

- **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:** 5 May 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-qwv5-f74g-8p86

## What is CVE-2026-7812?

CVE-2026-7812 is a medium-severity command injection vulnerability in 54yyyu code-mcp, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in 54yyyu code-mcp up to 4cfc4643541a110c906d93635b391bf7e357f4a8. The impacted element is the function git_operation of the file src/code_mcp/server.py of the component MCP Tool. Performing a manipulation of the argument operation results in command injection. The attack can be initiated remotely. The exploit has been made public and could be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-7812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7812 is a medium-severity command injection vulnerability in 54yyyu code-mcp, published on 5 May 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-7812 exists.

Affected product: 54yyyu code-mcp. 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-7812/ (Markdown: https://insights.sbomify.com/CVE-2026-7812/index.md)
```

## Sources

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

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