CVE-2026-60103 blender CVE debrief

Who should care

Users of Blender 3.0.0 through 5.1.2 should be aware of this vulnerability and take steps to mitigate it. Operators, platform administrators, vulnerability management teams, and security teams should review the vulnerability and implement compensating controls if necessary.

Technical summary

The vulnerability exists in the sdna_expand_names() function, where the member_index field is used as an array index into the sdna->members[] array without bounds validation. This allows any value outside the allocated range to produce an invalid pointer subsequently passed to strlen(), resulting in a SIGSEGV crash or unintended heap memory disclosure. The vulnerability can be triggered by supplying a crafted .blend file with a malicious signed short member_index value in the SDNA block.

Defensive priority

Medium

Recommended defensive actions

• Inventory and verify the Blender version
• Apply vendor patches or updates
• Implement compensating controls, such as monitoring and exception tracking
• Restrict access to .blend files
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-13T18:16:29.353Z and has not been modified since then. The NVD entry is currently Deferred. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The vulnerability exists in Blender 3.0.0 through 5.1.2, and attackers can trigger a crash or read adjacent heap memory by supplying a crafted .blend file with a malicious signed short member_index value in the SDNA block. The member_index field is used as an array index into the sdna->members[] array without bounds validation.

Official resources