Skip to content
Fencer Vulns
critical 9.8

CVE-2025-70067 json

Buffer Overflow vulnerability exists in Assimp versions up to 6.0.2 in the FBX Importer.

published 2026-05-04 6 mo ago modified 2026-11-04 4 d ago also EUVD-2025-209616

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

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

Patch / fix

  • assimp openSUSE Tumbleweed 6.0.5-2.1

opensuse advisories openSUSE-SU-2026:10739-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-70067 updated cvss 5.6

Assimp: Assimp: Buffer overflow in FBX Importer allows arbitrary code execution via crafted file.

  • Red Hat Enterprise Linux 10 qt6-qtquick3d
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 9 qt5-qt3d, qt5-qt3d-examples
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
6 mo ago

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Classification

Weakness
  • CWE-122 Heap-based Buffer Overflow

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.