Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2009-3850: Arbitrary Code Execution via .blend File in Blender

Published Nov 6, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v2
EPSS10.0%96th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Blender Foundation
IdentifiersCVE-2009-3850CWE-94 · Improper Control of Generation of…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Blender FoundationBlenderapplication
FAQ

Frequently asked questions

Is CVE-2009-3850 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-3850 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-3850?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2009-3850.
Is there a patch for CVE-2009-3850?
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.
What products are affected by CVE-2009-3850?
Blender Foundation Blender.
How severe is CVE-2009-3850?
CVE-2009-3850 has a CVSS v2 score of 9.3 (Critical) and an EPSS score of 10.0% (96th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.