CVE-2025-70070
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 FBXMeshGeometry.cpp, MeshGeometry::MeshGeometry()
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's FBX mesh parsing code. Specifically, the MeshGeometry::MeshGeometry() constructor in FBXMeshGeometry.cpp fails to properly handle malformed FBX files, likely due to missing bounds checking or validation during mesh geometry construction, causing a crash or hang when processing crafted input.
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.
-
Identify Assimp versionRun 'assimp version' from command line, or check the library version programmatically via aiGetVersion() or by inspecting the shared library binary (e.g., 'strings libassimp.so | grep -i "6.0"' or checking file metadata)Affected if The installed version is Assimp v6.0.2 exactly
-
Confirm FBX importer is availableCheck if the FBX importer module exists in the Assimp library directory (typically named 'libassimp_importer.so' or check 'assimp info --help' for FBX support listed), or verify the FBX file format handler is registered in your applicationAffected if The FBX importer module is present and loaded by the application
-
Determine if your application parses FBX filesReview application code or runtime configuration for any calls to Assimp's aiImportFile() or aiImportFileEx() with .fbx file extensions, or check if FBX files are processed in any data import pipelineAffected if The application or service imports or processes FBX files from any source
-
Assess source trust level of FBX filesIdentify whether FBX files come from untrusted sources (user uploads, external APIs, network endpoints, or any source outside your controlled asset pipeline)Affected if FBX files from untrusted or external sources are processed by Assimp
-
Check for crash/hang behavior with FBX inputIf currently experiencing unexplained crashes or hangs during FBX file loading, review application logs and crash dumps for faults occurring in Assimp's FBXMeshGeometry.cpp or MeshGeometry constructor codeAffected if Crashes or hangs occur specifically when loading FBX files through Assimp v6.0.2
You are affected if you run Assimp v6.0.2 and your application loads FBX files, especially from untrusted sources, as the vulnerability is triggered during mesh geometry construction in malformed FBX parsing.
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 dataAvoid processing untrusted or malformed FBX files with Assimp v6.0.2. Update to any patched version released by the Assimp project once available, or implement input validation/size limits on FBX meshes before passing to Assimp.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70070 — 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-70070 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