Assimp CVE-2025-15666

Exploitation requires local system access with at least low-privilege user credentials (PR:L per CVSS 4.0 vector), and the ability to supply a crafted 3D model file to an application that invokes Assimp's SceneCombiner::Copy function - this occurs during scene merging or duplication operations on model load. No user interaction beyond the application processing the file is required (UI:N). The attack is limited to local vectors; remote exploitation is only possible indirectly if a network-facing service passes user-supplied model files to Assimp for processing without local privilege escalation. Default configurations of Assimp itself are affected whenever the SceneCombiner code path is exercised with attacker-controlled width/height inputs. There is no requirement for a non-default configuration flag; the limiting factor is purely the local access prerequisite and the need to reach an Assimp-consuming application.

The CVSS 4.0 base score of 4.8 (Medium) reflects the constrained local attack vector (AV:L), low privilege requirement (PR:L), and limited per-system impact across confidentiality, integrity, and availability (VC:L/VI:L/VA:L). No scope change affects subsequent systems (SC:N/SI:N/SA:N). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, suggesting no confirmed in-the-wild exploitation campaign at time of analysis. However, the E:P exploit maturity modifier in the CVSS 4.0 vector confirms a public proof-of-concept exists (corroborated by the GitHub issue #6079 reference tagged as 'exploit'), which meaningfully lowers the barrier to exploitation. Real-world risk is moderate: exploitation is constrained to local access or to scenarios where an application using Assimp processes attacker-controlled model files. The most exposed environments are game engines, 3D content pipelines, or sandboxed rendering services that load user-uploaded assets. The combination of a public POC and no confirmed patch elevates urgency relative to the raw CVSS score alone.

A local attacker with low-privilege access to a system running an Assimp-based application - such as a 3D editor, game level loader, or asset pipeline service - crafts a malicious model file with specially manipulated width or height values. When the application loads this file and Assimp's SceneCombiner::Copy processes the scene data, the heap buffer is overflowed, potentially enabling arbitrary memory corruption that could lead to limited code execution or application crash. A public proof-of-concept demonstrating this behavior is available via the referenced GitHub issue.