dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-7066

HIGH · 7.3 CVSS v3.1 Published 2026-04-27
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 choieastsea simple-openstack-mcp up to 767b2f4a8154cca344344b9725537a58399e6036. The affected element is the function exec_openstack of the file server.py. The manipulation results in os command injection. It is possible to launch the attack remotely. The exploit has been made public and could be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not 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

OS command injection vulnerability in the exec_openstack function of server.py in simple-openstack-mcp up to commit 767b2f4a8154. The function processes user-controlled input without proper sanitization, allowing remote attackers to execute arbitrary OS commands.

MitigationReplace shell command execution with subprocess using argument lists (avoiding shell=True) and implement strict input validation on all parameters passed to exec_openstack before constructing any system 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 simple-openstack-mcp installation
    Search for server.py files in your environment that contain the exec_openstack function, or check for the simple-openstack-mcp package in your Python environment using 'pip show simple-openstack-mcp' or by searching for its installation directory
    Affected if The package or server.py with exec_openstack is present in your environment
  2. Identify the installed version or commit hash
    Check the git commit history if using a cloned repository, or look for version markers in the package metadata. Compare against commit 767b2f4a8154 - versions up to and including this commit are affected
    Affected if The installed version is at commit 767b2f4a8154 or earlier (no fix commit applied)
  3. Inspect server.py for the vulnerable exec_openstack function
    Open server.py and locate the exec_openstack function definition. Check if it directly passes user-controlled parameters to system command execution without sanitization
    Affected if The function exists and constructs shell commands using unsanitized input
  4. Verify shell=True is used in command execution
    Search for subprocess, os.system, os.popen, or similar calls within exec_openstack that use shell=True or string concatenation for command construction
    Affected if The code uses shell=True or concatenates strings into commands without input validation
  5. Confirm the function is callable from your deployment
    Check if exec_openstack is exposed via API endpoints, MCP tools, or other interfaces that accept external input
    Affected if The function accepts user input through any accessible interface

You are affected if simple-openstack-mcp with server.py containing the vulnerable exec_openstack function is installed at a version at or before commit 767b2f4a8154 and that function can receive external input.

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

Replace shell command execution with subprocess using argument lists (avoiding shell=True) and implement strict input validation on all parameters passed to exec_openstack before constructing any system commands.

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-7066 — 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-7066 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