dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10688

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable

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 determined in ahujasid blender-mcp up to 7636d13bded82eca58eb93c3f4cd8708dfdfbe8b. The impacted element is the function execute_blender_code of the file /src/blender_mcp/server.py. This manipulation of the argument code causes code injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. 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 · moderate confidence

A code injection vulnerability exists in the `execute_blender_code` function within `/src/blender_mcp/server.py` of the blender-mcp project. User-supplied input passed through the `code` argument is not properly sanitized before execution, allowing an attacker to inject and execute arbitrary code on the host system. This vulnerability is exploitable remotely and has been publicly disclosed.

MitigationImplement strict input validation and sanitization on the `code` parameter, preferably using a sandboxed execution environment (e.g., Docker container, restricted Python execution context) or a whitelist approach for allowed Blender commands/functions to prevent arbitrary code execution.

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Confirm blender-mcp installation
    Run 'pip show blender-mcp' or check your package manager for the blender-mcp package
    Affected if The package is not installed, but if it is installed, proceed to version check
  2. Check installed version
    Run 'pip show blender-mcp' to see the version number, then compare against any released versions after the vulnerability disclosure
    Affected if The installed version is older than the latest available version containing the fix, or if you cannot determine the version
  3. Locate the vulnerable server.py file
    Find the file at /src/blender_mcp/server.py in your installation directory (use 'pip show -f blender-mcp' to list installed files)
    Affected if The file exists and contains the execute_blender_code function
  4. Verify the execute_blender_code function lacks input sanitization
    Open server.py and inspect the execute_blender_code function - look for any validation, sanitization, or sandboxing of the 'code' parameter before execution
    Affected if The function passes the 'code' argument directly to exec(), eval(), or similar execution functions without sanitization
  5. Check if the vulnerable function is exposed
    Review your server configuration and API routes to determine if execute_blender_code is accessible via network API endpoints (HTTP/REST)
    Affected if The function is exposed via an API endpoint without authentication or additional access controls

You are affected if blender-mcp is installed and the execute_blender_code function in server.py accepts user input without sanitization and is accessible via an API endpoint or other remote interface.

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 on the `code` parameter, preferably using a sandboxed execution environment (e.g., Docker container, restricted Python execution context) or a whitelist approach for allowed Blender commands/functions to prevent arbitrary code execution.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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