ahujasid
blender-mcp
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at blender-mcp, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-66004 | 24 Jul 2026 | < 30a3308446cd8f81a9446e5a2ed657c0d8d86072 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-10688 | 2 Jun 2026 | 7636d13bded82eca58eb93c3f4cd8708dfdfbe8b | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-10662 | 2 Jun 2026 | 7636d13bded82eca58eb93c3f4cd8708dfdfbe8b | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-10661 | 2 Jun 2026 | 7636d13bded82eca58eb93c3f4cd8708dfdfbe8b | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.