dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-70067

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
Buffer Overflow vulnerability exists in Assimp versions up to 6.0.2 in the FBX Importer. The vulnerability occurs in aiMaterial::AddBinaryProperty, where a property key string from a crafted FBX file is copied into a fixed-size heap buffer using strcpy() without runtime length validation

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 · high confidence

A heap-based buffer overflow exists in Assimp's FBX importer (aiMaterial::AddBinaryProperty) where a property key string from a crafted FBX file is copied into a fixed-size buffer using strcpy() without any length validation, allowing an attacker to overwrite adjacent heap memory and potentially achieve code execution.

MitigationUpgrade Assimp beyond version 6.0.2 once a patched version is released; until then, avoid processing untrusted FBX files with affected versions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Assimp installation
    Check for Assimp libraries or tools on the system. Common locations include /usr/lib/, /usr/local/lib/, or installed via package managers (dpkg -l | grep assimp, rpm -qa | grep assimp). Also check for applications that link against libassimp.
    Affected if Assimp library (libassimp) or tools using it are present on the system
  2. Determine Assimp version
    Run 'assimp version' if the CLI tool is installed, or check the library version via 'dpkg -l libassimp*' or 'rpm -q libassimp'. If linked statically, inspect the binary or library file metadata.
    Affected if Version cannot be determined or is 6.0.2 or earlier
  3. Verify FBX import capability
    Confirm that the Assimp build includes FBX importer support. Check for FBX-related modules (look for fbx* files in /usr/lib/assimp or check 'assimp info --help' for FBX support).
    Affected if FBX importer module is present and loadable
  4. Check if untrusted FBX files are processed
    Audit any application or pipeline that uses Assimp to import FBX files from external or untrusted sources. Review application logs, code, or configuration for FBX file loading operations.
    Affected if The system or any application loads FBX files from external or untrusted sources using Assimp

A system is affected if it runs Assimp version 6.0.2 or earlier AND loads FBX files from external or untrusted sources using the FBX importer.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Assimp beyond version 6.0.2 once a patched version is released; until then, avoid processing untrusted FBX files with affected versions.

Recommended fix Moderate confidence

Latest stable Assimp release (check GitHub releases for post-6.0.2 version with CVE-2025-70067 fix)

  1. 1. Identify the current Assimp version in use by checking project dependencies or library version
  2. 2. Check if Assimp version is 6.0.2 or earlier, as these versions contain the vulnerability
  3. 3. Obtain the latest stable Assimp release from the official GitHub repository (github.com/assimp/assimp)
  4. 4. Upgrade Assimp to the latest stable release that addresses this vulnerability
  5. 5. Rebuild and redeploy the application using the patched Assimp library
  6. 6. Test the FBX import functionality to confirm the vulnerability is remediated
Caveat Minor - Assimp maintains backward compatibility for most use cases; verify no breaking changes in the release notes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-70067 — 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-70067 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