CVE-2026-66004 ahujasid CVE debrief

Who should care

Defenders responsible for maintaining and securing environments using BlenderMCP should assess exposure and prioritize updates. This includes reviewing the package version, assessing environment vulnerability, and implementing compensating controls as needed. Security teams should also monitor for suspicious activity related to API responses and perform regular security audits.

Why it matters

The BlenderMCP path traversal vulnerability allows attackers to write arbitrary files, potentially leading to persistent code execution.

• Verify and update BlenderMCP to prevent arbitrary file writes
• Assess exposure in environments using BlenderMCP
• Monitor for suspicious activity related to API responses

Technical summary

The BlenderMCP package before commit 30a3308 contains a path traversal vulnerability in the download_polyhaven_asset method. This allows attackers to write arbitrary files by injecting traversal sequences in API response include keys, potentially leading to persistent code execution. The vulnerability can be exploited through MITM attacks or prompt injection, allowing attackers to supply malicious paths like '../../.bashrc' to overwrite sensitive files. Defenders should prioritize verifying and updating BlenderMCP to commit 30a3308 or later.

Defensive priority

Defenders should prioritize verifying and updating BlenderMCP to commit 30a3308 or later, and assess exposure in their environments.

Recommended defensive actions

• Verify BlenderMCP version and update to commit 30a3308 or later
• Assess exposure in environments using BlenderMCP
• Monitor for suspicious activity related to API responses
• Perform vulnerability scanning to identify potential targets
• Review API response handling for potential injection vulnerabilities
• Implement additional logging and monitoring for API interactions
• Conduct regular security audits to detect similar vulnerabilities

Evidence notes

The BlenderMCP package vulnerability was reported on PyPI with a CVSS score of 6 and a severity of MEDIUM. The issue was fixed in commit 30a3308. Defenders should verify the package version and update to commit 30a3308 or later. Evidence is limited to public sources and may not reflect the full scope or impact of the vulnerability. Further verification is recommended.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.