CVE-2024-53425: assimp · n/a
Affects assimpSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubassimp/assimppkg:github/assimp/assimpOther threats | Affected
| Fixed in– |
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-2024-53425, organizations should: 1) Avoid processing untrusted or malformed MD5 model files until a patch is available. 2) Implement input validation and sanitization for all 3D model files before feeding them into Assimp. 3) Monitor software vendors and the Assimp project for security updates or patches addressing this vulnerability. 4) Employ application-level sandboxing or isolation to limit the impact of potential crashes caused by malformed inputs. 5) Conduct code reviews and static analysis on custom integrations of Assimp to detect similar buffer handling issues. 6) If feasible, upgrade to newer versions of Assimp once a fix is released, or apply any available backported patches. 7) Educate developers and users about the risks of processing untrusted 3D assets. 8) Use runtime protections such as AddressSanitizer or other memory error detection tools during development and testing to catch similar issues early.
Description
A heap-buffer-overflow vulnerability was discovered in the SkipSpacesAndLineEnd function in Assimp v5.4.3. This issue occurs when processing certain malformed MD5 model files, leading to an out-of-bounds read and potential application crash.