CVE-2026-119722
Description
A flaw was found in Blender. This vulnerability allows an attacker to achieve arbitrary code execution or cause a Denial of Service (DoS) by convincing a user to open a specially crafted project file. Because the application fails to properly validate structure sizes during file parsing, memory overruns occur on the heap, potentially compromising system integrity.
Statement
This vulnerability is rated as Important severity because successful exploitation allows arbitrary code execution within the context of the running user session, though it requires user interaction rather than being directly exploitable over the network. In Red Hat environments, Blender is available as an optional package in EPEL and Fedora rather than standard enterprise server deployments, confining exposure to workstations processing external media assets. Impact is constrained to the permissions and filesystem access privileges granted to the user launching the application.
Mitigation
--- CME Mitigation Guidance (2026-11-03) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to enforce structure size validation during SDNA struct parsing in read_struct(): upgrade to Blender 4.5.15 and 5.2.3 (or the fixed Blender builds), which validates structure sizes in read_struct() even when SDNA struct layouts compare equal to prevent heap overruns on short blocks, closing crafted .blend project file with short blocks. Until patched, this is a concern on workstations and user sessions opening untrusted .blend project files, so restrict opening untrusted or externally sourced .blend files and prevent processing unvetted media assets. As a compensating measure, enable ASLR to randomize userspace memory layout and prevent reliable targeting of predictable heap addresses, enforce full RELRO and PIE to protect the Global Offset Table from being overwritten during heap corruption, deploy Control Flow Integrity or Shadow Call Stack to restrict indirect branch targets and mitigate ROP/JOP execution, configure EDR agents to monitor for and detect anomalous child processes or shell executions spawned from Blender, and enforce NX/XD bit protections to ensure heap and data memory regions remain non-executable. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap out-of-bounds access defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
