LiveActive security incident?Get immediate response
CVE Record

CVE-2025-70071: An issue in Assimp v.6.0.2 allows a remote attacker to cause a denial of service via the FBXParser.cpp, Par...

An issue in Assimp v.6.0.2 allows a remote attacker to cause a denial of service via the FBXParser.cpp, ParseVectorDataArray()

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-70071 is a denial-of-service issue reported in Assimp v6.0.2 when parsing FBX data. If a system automatically processes attacker-supplied 3D model files, a crafted input may exhaust resources or crash parsing, interrupting availability. The sources do not show data theft, code execution, or confirmed active exploitation.

Executive priority

Prioritize remediation where Assimp processes untrusted files in customer-facing or automated workflows. The main business risk is service disruption, not confidentiality loss, based on current sources.

Technical view

The issue is described in Assimp v6.0.2, specifically FBXParser.cpp ParseVectorDataArray(). CVSS 3.1 is 7.5: network attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high availability impact only. Listed CWEs include improper input validation and uncontrolled resource allocation/resource consumption.

Likely exposure

Exposure is most likely in applications, pipelines, or services that use Assimp v6.0.2 to parse untrusted or remotely supplied FBX/3D model content. The bundle does not identify packaged product CPEs or downstream affected vendors.

Exploitation context

The source bundle includes a public researcher gist and Red Hat tracking, but KEV is false and no cited source confirms exploitation in the wild. Treat exploit status as unconfirmed while prioritizing internet-facing or automated file-processing paths.

Researcher notes

Evidence is limited to the CVE metadata and referenced tracker materials. The affected product field is incomplete, so downstream exposure must be established by dependency inventory. Avoid assuming affected bundled products without vendor confirmation.

Mitigation direction

  • Check Assimp and OS vendor guidance for a fixed version or backported package.
  • Limit or disable untrusted FBX ingestion until remediation is confirmed.
  • Run 3D parsing in isolated workers with strict CPU, memory, and timeout limits.
  • Restrict upload sources, file types, and maximum file sizes where business workflows allow.
  • Add monitoring for parser crashes, timeouts, and repeated failed FBX processing.

Validation and detection

  • Inventory direct and transitive use of Assimp, especially v6.0.2.
  • Identify services that parse FBX or 3D assets from remote users or partners.
  • Check Red Hat and upstream Assimp advisories for package status and fixes.
  • Review logs for crashes, memory exhaustion, or timeouts in model-import workflows.
  • After updating, run regression tests against valid and malformed FBX samples safely.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1284: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-70071 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-70071Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPAssimp: Assimp: Denial of Service via FBXParser.cpp ParseVectorDataArray() function
other:Red Hat severity ratingcvssV3_1
  • 2026-05-04T16:01:04.368Z: Reported to Red Hat.
  • 2026-05-04T00:00:00.000Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1284 · source CWE mapping

Improper Validation of Specified Quantity in Input

Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.