Path Traversal in blender-mcp (CVE-2026-66004)
Summary
Path traversal in blender-mcp (CVE-2026-66004). Data can be tampered with by attackers. Mitigation: upgrade to 1.6.5 or later.
Original description
The description as published by the source.
BlenderMCP before commit 30a3308 contains a path traversal vulnerability in the download_polyhaven_asset method that allows attackers to write arbitrary files by injecting traversal sequences in API response include keys. Attackers performing MITM attacks or prompt injection can supply malicious paths like '../../.bashrc' to overwrite sensitive files and achieve persistent code execution.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-66004 has been found in blender-mcp.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: upgrade blender-mcp to 1.6.5 or later.
If unsure, ask your IT team or search "blender-mcp CVE-2026-66004" on the vendor's site.
CVE-2026-66004 (blender-mcp) — CWE-22 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.6.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in blender-mcp.
Check the vendor advisory for the affected versions of blender-mcp.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to 1.6.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'blender-mcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'blender-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
blender-mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade blender-mcp to 1.6.5ステージング環境で 1.6.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web vulncheck.com