Skip to main content
VulnerabilityPublished Updated

CVE-2025-15538: Open Asset Import Library Assimp · Use After Free

Affects Open Asset Import Library AssimpSource CVE Database V5

0

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Open Asset Import LibraryAssimpAffected
  • =6.0.0
  • =6.0.1
  • =6.0.2
Fixed in–
GitHubassimp/assimppkg:github/assimp/assimpOther threatsAffected
  • =6.0.0
  • =6.0.1
  • =6.0.2
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:assimp:assimp:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-15538, organizations should: 1) Monitor the Assimp project repository and security advisories for official patches or updates addressing this vulnerability and apply them promptly. 2) Restrict local access to systems running Assimp, especially in multi-user environments, to trusted personnel only. 3) Employ application whitelisting and sandboxing techniques to limit the impact of potential exploitation. 4) Implement strict input validation and sanitization on 3D asset files before processing them with Assimp to reduce malformed input risks. 5) Use runtime memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to hinder exploitation attempts. 6) Conduct regular security audits and monitoring for unusual behavior or crashes related to Assimp usage. 7) Educate developers and system administrators about the vulnerability and the importance of applying updates and following secure coding practices when integrating Assimp.

Description

A security vulnerability has been detected in Open Asset Import Library Assimp up to 6.0.2. Affected by this vulnerability is the function Assimp::LWOImporter::FindUVChannels of the file /src/assimp/code/AssetLib/LWO/LWOMaterial.cpp. Such manipulation leads to use after free. The attack needs to be performed locally. The exploit has been disclosed publicly and may be used. This and similar defects are tracked and handled via issue #6128.

References

Community reviews

Loading reviews…