# CVE-2025-70069: Denial of service in n/a

> A remote attacker can cause a denial of service in the Assimp library via the FBXConverter component, affecting applications using this library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** DEBIAN-CVE-2025-70069, GHSA-797v-2v4c-3xvx, UBUNTU-CVE-2025-70069

## What is CVE-2025-70069?

CVE-2025-70069 is a high-severity denial of service vulnerability in n/a, published on 4 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Assimp v.6.0.2 allows a remote attacker to cause a denial of service via the FBXConverter.cpp and ConvertMeshMultiMaterial() method

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input), CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-70069?


## How do I fix CVE-2025-70069?

Upgrade to a fixed version.

## Is CVE-2025-70069 being exploited?

There is no known exploitation of CVE-2025-70069 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70069 and fix it if it is affected.

What it is: CVE-2025-70069 is a high-severity denial of service vulnerability in n/a, published on 4 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-70069 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-70069/ (Markdown: https://insights.sbomify.com/CVE-2025-70069/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-70069
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-70069
- OSV: https://osv.dev/vulnerability/CVE-2025-70069

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-70069/
Summaries are generated and may contain mistakes; the official description above is the record.