Arbitrary Code Execution via .blend File in Blender
Blender versions 2.34, 2.35a, 2.40, and 2.49b are vulnerable to arbitrary code execution when opening a specially crafted .blend file. The vulnerability arises because Python statements embedded in the onLoad action of a ScriptLink SDNA are executed automatically when the file is loaded, allowing attackers to run arbitrary Python code on the victim's system.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote attackers to execute arbitrary code on the target system with the privileges of the user running Blender. This can lead to full system compromise, data theft, or further malware installation.
If you can’t patch tonight, do this now.
Users should avoid opening .blend files from untrusted sources. Additionally, Blender can be configured to disable the automatic execution of Python scripts on file load, reducing the risk of exploitation.
Patch, then assume compromise.
Upgrade to a version of Blender that properly restricts or sanitizes the execution of embedded Python code in .blend files, or disables the automatic execution of Python scripts on file load.
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.