Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDistribute malicious .blend plus crafted point cache
-
DeliveryVictim opens scene file in Blender
-
ExploitInteger overflow in ptcache_data_alloc() undersizes buffer
-
ExecutionHeap buffer overflow during point cache read
-
ImpactExecute code as the user
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to open, within an affected Blender version (before 4.5.15, or 5.x before 5.2.3), a malicious point cache file carrying an abnormally large totpoint value alongside an attacker-supplied .blend file; the oversized value drives the integer overflow in ptcache_data_alloc() during point cache reading. Limiting factors confirmed by the CVSS vector: the attack is local (AV:L) and requires passive user interaction (UI:P) - there is no network or remote trigger, and the attacker must induce the user to load the crafted files. PR:N means no authentication is needed once the file is opened. The only complete fix stated by the evidence is updating to a fixed version. |
| Impact | This is a genuine but conditional priority rather than a drop-everything emergency. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H) scores 8.5 because the three impact metrics are all High (code execution as the user), but exploitation is gated by two factors the base score makes explicit: the attack vector is Local (AV:L) and passive user interaction is required (UI:P) - the victim must open an attacker-supplied .blend file plus a crafted point cache file. There is no remote/network path. No EPSS probability was supplied and the CVE is not listed in CISA KEV, so there is no signal of active or widespread exploitation; the only exploitation framework signal present is the vuln.today decision label 'this_week', which argues for prompt but not emergency patching. The report originates from VulnCheck, a credible research source, and a vendor patch exists. Net assessment: a real memory-corruption flaw with code-execution potential in a very widely used product, but realistic risk depends entirely on social-engineering a user into opening malicious scene files, so it is a patch-this-week item, not an actively-exploited internet-facing crisis. |
| Exploit ScenarioDerived | An attacker distributes a Blender scene - for example a free model, asset pack, or project file shared on a marketplace or forum - that bundles a malicious point cache file crafted with an oversized totpoint value. When the victim opens the .blend file in an unpatched Blender, the integer overflow in ptcache_data_alloc() undersizes a heap buffer that is then overflowed, crashing Blender or executing code with the victim's privileges. No public exploit was identified at time of analysis; the described trigger comes from the VulnCheck advisory and vendor commits. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
A heap buffer overflow in Blender's point cache loading path, driven by an integer overflow in ptcache_data_alloc(), affects all versions before 4.5.15 and 5.x releases before 5.2.3. An attacker who supplies a crafted point cache file with an abnormally large totpoint value alongside a .blend file can crash the application or execute code with the privileges of the user who opens it; the attack is local (AV:L) and requires the victim to open the attacker-supplied files (UI:P), with no authentication needed once the files are loaded. No public exploit code or active exploitation has been identified at time of analysis, and Blender has published fixes for both affected branches.
RemediationAI
Vendor-released patch: update to Blender 4.5.15 for the 4.5 branch or 5.2.3 for the 5.x branch; the fixes are delivered through pull request https://projects.blender.org/blender/blender/pulls/164279 and commits https://projects.blender.org/blender/commit/a0c62db3db61803f86e874bc05407890ce4a1e43 and https://projects.blender.org/blender/commit/4f8a3270213b1ee67b44fe122ace3debdec3de47, with supporting detail in the VulnCheck advisory at https://www.vulncheck.com/advisories/blender-before-4.5.15-and-5-x-before-5.2.3-heap-buffer-overflow-via-point-cache. Updating to a fixed version is the only complete remediation stated by the available evidence; because exploitation requires the victim to open an attacker-supplied .blend file together with its crafted point cache, limiting the opening of .blend files and cache data received from untrusted sources reduces exposure but does not remove the underlying integer overflow, and this should be treated as a stopgap until the affected installations are upgraded to 4.5.15 or 5.2.3.
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 point cache subsystem stores baked simulation data in companion cache files referenced by a .blend scene. When reading such a file, ptcache_data_alloc() computes the allocation size from the cached totpoint count; a crafted file can carry a totpoint value large enough that the size arithmetic wraps (CWE-190, integer overflow), producing a heap allocation smaller than the data subsequently written into it and yielding a heap-based buffer overflow. The root cause class is integer overflow leading to an undersized allocation, so the resulting memory corruption is reachable purely through file parsing rather than through network input. The CPE cpe:2.3:a:blender_foundation:blender identifies the affected product line, with vulnerable ranges covering releases before 4.5.15 and 5.x releases before 5.2.3. The CVSS:4.0 vector rates the flaw AV:L/AC:L/AT:N/PR:N/UI:P with high confidentiality, integrity and availability impact confined to the vulnerable component, and the independent assessment aligns with CVSS:3.1 AV:L/AC:L/PR:N/UI:R, confirming that exploitation is gated by the victim opening the crafted files rather than by any remote or pre-authentication pathway. The specific trigger sequence beyond loading a malicious point cache alongside a .blend file is not further described in the available sources.
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:H/VI:H/VA:H/SC:N/SI:N/SA:N
Local file-parsing flaw triggered when a user opens crafted files, so AV:L and UI:R with PR:N; memory corruption yields code execution as the user, giving C:H/I:H/A:H.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Blender before 4.5.15 and 5.x before 5.2.3 contains a heap buffer overflow vulnerability caused by integer overflow in ptcache_data_alloc() when reading point cache files. Attackers can supply a crafted point cache file with a large totpoint value alongside a .blend file to crash Blender or execute code as the user.
Executive ViewAI
A high-severity heap buffer overflow (CVE-2026-119718) in Blender's point cache loading affects all versions before 4.5.15 and 5.x releases before 5.2.3, enabling arbitrary code execution when a user opens a malicious .blend file. This puts any employee using Blender-particularly in design, animation, and engineering teams-at risk of local compromise with user-level privileges, potentially leading to data theft or lateral movement. Leadership should prioritize patching because the exploit requires only user interaction and could be distributed via email or shared files.
Apply vendor patch.
Threat Intelligence Overview
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.
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
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 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 heap reads in Blender's .blend file loader let a crafted file crash the application or leak process memory
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
EUVD-2026-114123
GHSA-998f-5325-f384
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB