dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-70071

MEDIUM · 5.9 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An issue in Assimp v.6.0.2 allows a remote attacker to cause a denial of service via the FBXParser.cpp, ParseVectorDataArray()

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 confidence

A denial of service vulnerability exists in Assimp v6.0.2 within the FBXParser.cpp ParseVectorDataArray() function. Remote attackers can trigger the vulnerability by providing a specially crafted malformed FBX file that causes the parser to crash or enter an unresponsive state during vector data array parsing.

MitigationUpgrade to a patched version of Assimp that addresses the vulnerability in FBXParser.cpp. Until a patch is available, avoid processing untrusted FBX files with Assimp v6.0.2.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Assimp version
    Run 'assimp version' or check the library binary metadata (e.g., 'strings libassimp.so | grep version' or check file properties of assimp.dll)
    Affected if The version is v6.0.2 exactly
  2. Confirm FBX import capability is present
    Check if Assimp was built with FBX support by running 'assimp info --help' and looking for FBX in supported formats, or inspect the loaded modules/plugins for FBXParser
    Affected if FBX file import capability is enabled in the Assimp installation
  3. Locate FBXParser component
    Search for FBXParser.cpp or libFBXParser (depending on build system) in the Assimp installation directory or library path
    Affected if The FBXParser component exists in the environment and is being used
  4. Test FBX file parsing behavior
    Attempt to load a valid FBX file using the Assimp command line tool ('assimp info <file.fbx>') or API to confirm FBX parsing is functional
    Affected if FBX files can be parsed by the Assimp installation in use

You are affected if Assimp v6.0.2 is installed and FBX file parsing is enabled, as the vulnerability resides in the FBXParser ParseVectorDataArray function used during FBX import.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Assimp that addresses the vulnerability in FBXParser.cpp. Until a patch is available, avoid processing untrusted FBX files with Assimp v6.0.2.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-70071 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-70071 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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