CVE-2025-70072
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in Assimp v.6.0.2 allows a remote attacker to cause a denial of service via the FBXConverter.cpp, FBXConverter::ConvertMeshMultiMaterial() components
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA denial-of-service vulnerability exists in Assimp v6.0.2 within the FBXConverter::ConvertMeshMultiMaterial() function in FBXConverter.cpp. The vulnerability is triggered during FBX file parsing when processing multi-material mesh data, likely due to improper bounds checking or an infinite loop condition in the material conversion logic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Assimp versionRun 'assimp version' from command line, or check the library binary version metadata (e.g., via 'strings' on libassimp.so or equivalent), or inspect the AssimpConfig.cmake version file if using CMake integrationAffected if the version is 6.0.2 exactly or falls within the v6.0.x release line prior to the security patch
-
Identify FBX import capability in useSearch application code or build configuration for Assimp FBX importer usage (look for aiImportFile with .fbx extensions, or FBX in supported format lists)Affected if the application uses Assimp to import or convert FBX files
-
Confirm multi-material mesh processing occursReview the specific FBX models being processed, or add logging around FBXConverter::ConvertMeshMultiMaterial() calls to observe material index handling during parsingAffected if FBX files containing meshes with multiple material assignments (multi-material meshes) are being parsed
-
Check for resource exhaustion symptomsMonitor CPU usage and process hang status during FBX parsing; examine process logs for timeout or infinite loop indicators when processing multi-material FBX contentAffected if parsing multi-material FBX files causes sustained high CPU usage or apparent hangs indicative of an infinite loop
A user is affected if running Assimp v6.0.x on multi-material FBX files, as the ConvertMeshMultiMaterial function lacks proper bounds checking and can enter an infinite loop during material conversion.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Assimp to the latest version containing the security patch. If an upgrade is not immediately feasible, restrict processing of untrusted FBX files and implement resource limits/timeouts for model parsing operations.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-70072 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data