Quick answers
- Is CVE-2026-10688 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10688 being exploited in the wild.
- How severe is CVE-2026-10688?
- Medium severity, with a CVSS score of 5.5, published 2 June 2026.
- Which products and versions are affected?
- Ahujasid Blender-Mcp up to 7636d13bded82eca58eb93c3f4cd8708dfdfbe8b.
- Is there a fix for CVE-2026-10688?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-10688 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-10688?
- Check whether you run Ahujasid Blender-Mcp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A code injection vulnerability exists in blender-mcp up to commit 7636d13bded82eca58eb93c3f4cd8708dfdfbe8b. The root cause is the use of Python's exec() function within the execute_blender_code function in /src/blender_mcp/server.py, which processes user-controlled input without sanitization or sandboxing. An attacker can exploit this by providing a malicious 'code' argument via the MCP client, which is then forwarded to the Blender addon and executed with the privileges of the Blender process. This allows for arbitrary system command execution through modules like 'os' or 'subprocess'. While the attack is network-reachable, it may require low-level authentication or user interaction via indirect prompt injection. No official patch has been confirmed by the vendor.
Affected products
- ahujasid blender-mcp up to 7636d13bded82eca58eb93c3f4cd8708dfdfbe8b
Timeline
- 2026-03-10: disclosed: Issue reported on GitHub repository
- 2026-06-02: advisory: CVE published by VulDB/NVD