Application crash via freed BVH channel vector
Published Jun 16, 2025 · Updated Jun 16, 2025
Use-after-free in Assimp 5.4.0 through 5.4.3 allows local users to crash applications that import a crafted BVH file. Recursive child-node insertion reallocates the node vector, leaving a stale pNode reference that ReadNodeChannels uses to push values into the freed mChannels vector. Reachability requires an untrusted BVH asset to enter a local import workflow; the demonstrated consequence is a process crash, not confirmed code execution.
Summary
What happened
Use-after-free in Assimp 5.4.0 through 5.4.3 allows local users to crash applications that import a crafted BVH file. Recursive child-node insertion reallocates the node vector, leaving a stale pNode reference that ReadNodeChannels uses to push values into the freed mChannels vector. Reachability requires an untrusted BVH asset to enter a local import workflow; the demonstrated consequence is a process crash, not confirmed code execution.
The record
- CVE
- CVE-2025-6119
- Published
- Jun 16, 2025
- Updated
- Jun 16, 2025
- Vendor
- Open Asset Import Library
- Product
- Assimp
- Classifications
- CWE-119, CWE-416, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 16, 2025CVE publishedPublication date reported by the CVE source.
- Jun 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.4.0
- Affected versionversion=5.4.1
- Affected versionversion=5.4.2
- Affected versionversion=5.4.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Assimp BVH heap-use-after-free reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo