dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-7590

HIGH · 7.3 CVSS v3.1 Published 2026-05-01
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 identified in eyal-gor p_69_branch_monkey_mcp up to 69bc71874ce40050ef45fde5a435855f18af3373. The affected element is an unknown function of the file branch_monkey_mcp/bridge_and_local_actions/routes/advanced.py of the component Preview Endpoint. Such manipulation of the argument dev_script leads to os command injection. The attack can be launched remotely. The exploit is publicly available and might be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. 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

A command injection vulnerability exists in the Preview Endpoint of branch_monkey_mcp (advanced.py) where the dev_script argument is passed unsafely to OS command execution. Attackers can inject arbitrary shell commands via this parameter, leading to complete system compromise.

MitigationSanitize and validate the dev_script input before passing to any OS command execution functions. Prefer using subprocess with shell=False and passing arguments as a list, or implement strict allow-listing of permitted values.

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 branch_monkey_mcp package installation
    Use pip show branch_monkey_mcp or python -c "import branch_monkey_mcp; print(branch_monkey_mcp.__file__)" to find where the package is installed
    Affected if The package is not installed, then the environment is not affected by this CVE
  2. Identify the installed version of branch_monkey_mcp
    Run pip show branch_monkey_mcp and note the Version field, or import the package and check its __version__ attribute if available
    Affected if The installed version falls within any affected version range (compare to the fixed version once available)
  3. Locate the vulnerable advanced.py file
    Find advanced.py within the branch_monkey_mcp package directory - this file contains the Preview Endpoint with the command injection flaw
    Affected if advanced.py is not found in the package, the vulnerability may not be present
  4. Inspect the Preview Endpoint implementation in advanced.py
    Open advanced.py and search for the Preview Endpoint function; locate where the dev_script parameter is passed to OS command execution functions (such as os.system, subprocess with shell=True, or similar)
    Affected if The dev_script argument is passed directly to any OS command execution function without sanitization, validation, or use of shell=False, then the environment is vulnerable
  5. Determine if the Preview Endpoint is exposed
    Check the application configuration or routing to see if the Preview Endpoint is registered and accessible (check for route definitions like /preview, /preview_endpoint, or similar in the application's main entry point or API definitions)
    Affected if The Preview Endpoint is accessible and the code in step 4 shows unsafe handling of dev_script, then the environment is vulnerable to command injection

The environment is affected if branch_monkey_mcp is installed with a version that includes the vulnerable Preview Endpoint in advanced.py, where dev_script is passed unsafely to OS command execution without sanitization or shell=False protection.

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

Sanitize and validate the dev_script input before passing to any OS command execution functions. Prefer using subprocess with shell=False and passing arguments as a list, or implement strict allow-listing of permitted values.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7590 — 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-7590 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