dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7812

HIGH · 7.3 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Command injection vulnerability in the git_operation function within src/code_mcp/server.py of the code-mcp project. The 'operation' argument is not properly sanitized before being used in git operations, allowing remote attackers to inject arbitrary shell commands.

MitigationImplement strict input validation and sanitization for the operation argument, preferably using a whitelist approach for allowed git operations, and avoid passing unsanitized user input to shell commands.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the code-mcp installation
    Find the src/code_mcp/server.py file in your environment. Common locations include Python site-packages, project directories, or container images where code-mcp is deployed.
    Affected if The file exists and contains a git_operation function definition
  2. Identify the installed version
    Check the package version via 'pip show code-mcp' or inspect the version field in the project's __init__.py, setup.py, or pyproject.toml if present.
    Affected if The version is unknown, unpatched, or falls within a vulnerable range where the operation argument lacks sanitization
  3. Examine the git_operation function
    Open src/code_mcp/server.py and locate the git_operation function. Inspect how the 'operation' parameter is handled - look for direct use in subprocess calls, os.system, or shell execution without validation.
    Affected if The operation argument is passed directly to shell commands without sanitization or whitelist validation
  4. Check if git_operation is reachable
    Review how git_operation is called in your application. Trace the call chain from user-facing endpoints or entry points to determine if external input can reach the operation parameter.
    Affected if User-supplied input can flow to the operation argument without validation
  5. Audit input handling around git operations
    Search the codebase for patterns like subprocess.run, os.popen, or shell=True usage with the operation variable. Verify if any input validation or escaping exists before the git command execution.
    Affected if No input validation, escaping, or whitelist filtering is applied to the operation argument before shell execution

You are affected if the code-mcp server.py file exists with a vulnerable git_operation function where the operation parameter is used in shell commands without sanitization and external input can reach it.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for the operation argument, preferably using a whitelist approach for allowed git operations, and avoid passing unsanitized user input to shell commands.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7812 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data