EUVD-2026-114126
GHSA-8hxf-4775-5j3p
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted .blend file to user
-
DeliveryUser browses or appends from file
-
ExploitAccessors read ID fields past block length
-
ExecutionHeap out-of-bounds read triggered
-
ImpactCrash or heap memory disclosure
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a user of Blender (before 4.5.15, or 5.x before 5.2.3) to open/browse or append data from an attacker-crafted .blend file containing short ID blocks; the file-browse or append-from-library workflow is what invokes the vulnerable blo_bhead_id_* accessors in readfile.cc. No authentication or elevated privileges are needed (PR:N), but the attack is local and file-based (AV:L) and gated by required user interaction (UI:P) - the victim must be convinced to handle the malicious file. This limits realistic risk to social-engineering or supply-chain distribution of .blend assets rather than remote or automated exploitation; it is not triggerable against a network service and affects no subsequent systems. |
| Impact | This is a moderate-priority issue rather than an emergency. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P, score 6.9) describes a local, low-complexity flaw with no privileges required but passive user interaction - the victim must open, browse, or append from a malicious .blend file, so it cannot be triggered remotely or unauthenticated against a service. Impact is skewed toward availability (VA:H, crashes) with only limited confidentiality exposure (VC:L, heap memory disclosure) and no integrity impact, consistent with the CWE-125 out-of-bounds read. The vuln.today decision label is 'this_month' (not act_now or emergency), and there is no CISA KEV listing and no public exploit identified, which aligns with a file-parsing bug that depends on social-engineering a user into handling a crafted file. No EPSS score was provided in the input, so exploitation probability cannot be quantified here. The signals are internally consistent: a medium-severity, interaction-dependent client-side bug in a desktop application, worth patching on a normal cycle rather than as a drop-everything fire. |
| Exploit ScenarioDerived | An attacker crafts a malicious .blend file with short ID blocks and distributes it (e.g., via a shared asset pack, marketplace download, or project file) to a Blender user. When the victim browses or appends data from that file, Blender's blo_bhead_id_* accessors read ID fields past the block boundary, causing a heap over-read that crashes Blender or discloses adjacent heap memory. No public exploit code was identified in the provided data; exploitation requires the user to open or append from the attacker-supplied file. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
Out-of-bounds heap reads in Blender's .blend file loader let a crafted file crash the application or leak process memory, affecting releases before 4.5.15 and 5.x before 5.2.3. The weakness sits in the blo_bhead_id_* accessors in readfile.cc, which consume ID block fields without first checking that the block is long enough; a .blend file containing deliberately short ID blocks triggers the over-read when a victim browses or appends data from it. No authentication or elevated privileges are required (PR:N), but exploitation is local and file-based (AV:L) and requires the user to open or append from a malicious asset (UI:P), so realistic exposure is social engineering or supply-chain distribution of .blend content rather than remote attack; no public exploit code or KEV listing was identified at time of analysis, and this is a moderate-priority issue rather than an emergency, with vendor patches available.
RemediationAI
Vendor-released patch: upgrade to Blender 4.5.15 (for the 4.5 LTS branch) or 5.2.3 (for 5.x); both versions contain the length checks added to the blo_bhead_id_* accessors in readfile.cc, with the changes visible in pull request https://projects.blender.org/blender/blender/pulls/164279 and commits c5d6faf04bf3f17efb6c404896ef0e7427784da5, 7de4986e74ed47f67e78eb4b76609bb6d1ae8a0e, 495deb9efff880c42aa88110aec0ea2c0fb1eb07, and 94d99b362b0d236dcf07a96c1c8f9f5389d0583c, and summarized in the VulnCheck advisory at https://www.vulncheck.com/advisories/blender-before-4.5.15-and-5-x-before-5.2.3-out-of-bounds-read-via-blo-bhead-id-accessors. Because the trigger is a malicious .blend file that the user opens, browses, or appends from, installations that cannot be updated immediately should treat .blend assets of unknown provenance as untrusted and avoid opening or appending from them until the patched build is deployed; note that this is a procedural control only - it does not fix the parser and depends entirely on user and pipeline discipline, so it should be treated as a stopgap until 4.5.15 or 5.2.3 is installed. Remediation can be scheduled within the month given the local, user-interaction-gated nature of the issue and the absence of KEV or public exploit reporting.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Blender's native .blend format is a sequence of tagged blocks, each prefixed by a BHead header that records the block code, length, and an ID name used to identify datablocks (objects, meshes, libraries, and so on). In readfile.cc, the blo_bhead_id_* accessor family reads the ID fields out of these headers, and prior to the fix it did so without verifying that the declared block length actually covers the ID bytes being accessed. Supplying a file whose ID blocks are shorter than the accessor expects causes reads past the end of the allocated heap buffer - the CWE-125 out-of-bounds read class. The consequence maps directly onto the assessed impact: out-of-bounds reads can terminate the process (availability: high, A:H) and can surface adjacent heap contents back into the application or resulting data (confidentiality: low, C:L), while integrity is unaffected (I:N). The vulnerable path is the file-reading/browsing and append-from-library workflow rather than any network-facing service, which is consistent with the local, user-interaction-gated vector. The affected code is shared across the 4.5 LTS branch and the 5.x line, hence the two separate fixed versions.
Know when Blender gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
Local file-parsing bug needing a user to open/append a crafted .blend (AV:L, UI:R, PR:N); heap over-read gives limited disclosure (C:L) and reliable crashes (A:H), no integrity impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Blender before 4.5.15 and 5.x before 5.2.3 contains an out-of-bounds read vulnerability in blo_bhead_id_* accessors in readfile.cc that read ID fields without block length checks. Attackers can supply a crafted .blend file with short ID blocks that, when browsed or appended from, causes heap over-reads leading to crashes or heap memory disclosure.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Endless Infinite loop in Blender-thumnailing due to logical bugs. Rated high severity (CVSS 7.5), this vulnerability is
A flaw was found in Blender 3.3.0. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authen
A flaw was found in Blender 3.3.0. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authen
Heap out-of-bounds memory access in Blender's .blend file parsing path (read_struct()) can crash Blender or potentially
Heap-based buffer overflow in Blender's .blend thumbnail extractor (blender-thumbnailer and the Windows shell extension)
A heap buffer overflow in Blender's point cache loading path, driven by an integer overflow in ptcache_data_alloc(), aff
A missing bounds check in the image loader used in Blender 3.x and 2.93.8 leads to out-of-bounds heap access, allowing a
An integer overflow in the processing of loaded 2D images leads to a write-what-where vulnerability and an out-of-bounds
Out-of-bounds read in Blender 3.0.0 through 5.1.2 allows an attacker to crash the application or disclose heap memory co
Opening a crafted .blend file in a vulnerable Blender build causes a heap out-of-bounds read inside read_file_dna() and
An integer underflow in the DDS loader of Blender leads to an out-of-bounds read, possibly allowing an attacker to read
Exploit-DB