CVE-2009-3850 json
Blender 2.34, 2.35a, 2.40, and 2.49b allows remote attackers to execute arbitrary code via a .blend file that contains Python statements in…
published 2009-11-06 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-3821
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.0%
- EPSS 10.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
Blender 2.34, 2.35a, 2.40, and 2.49b allows remote attackers to execute arbitrary code via a .blend file that contains Python statements in the onLoad action of a ScriptLink SDNA.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2009-3850 updated cvss 5.8
Blender: Arbitrary code execution via malicious .blend file
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Timeline
- First public exploit (EDB-9843)
- Published
Exploit prediction
9.98% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-9843 Blender 2.34/2.35a/2.4/2.49b - '.blend' Command Injection remote, 2009-11-05
- coresecurity.com http://www.coresecurity.com/content/blender-scripting-injection referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
coresecurity.com
/content/blender-scripting-injection
exploit
-
securityfocus.com
/bid/36838
vdb-entry
-
securityfocus.com
/archive/1/507706/100/0/threaded
mailing-list
Sources
- CVE List CVE-2009-3850
- NVD CVE-2009-3850
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.