# CVE-2025-3196: Open Asset Import Library Assimp Malformed File MD2Loader.cpp InternReadFile stack-based overflow

> A stack-based buffer overflow in Assimp's MD2 loader allows attackers to execute arbitrary code or cause denial of service via a malformed file.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Apr 2025
- **Updated:** 23 Jul 2025
- **Also known as:** DEBIAN-CVE-2025-3196, GHSA-hj96-872g-wqc5, PYSEC-2025-170, UBUNTU-CVE-2025-3196

## What is CVE-2025-3196?

CVE-2025-3196 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 4 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in Open Asset Import Library Assimp 5.4.3. Affected is the function Assimp::MD2Importer::InternReadFile in the library code/AssetLib/MD2/MD2Loader.cpp of the component Malformed File Handler. The manipulation of the argument Name leads to stack-based buffer overflow. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

1 open source package ship an affected version, including pyassimp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyassimp` | PyPI | All versions to 5.4.3 | None |

Products: Assimp Assimp.

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

Upgrade to a fixed version.

## Is CVE-2025-3196 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3196 exists.

## Other vulnerabilities in Open Asset Import Library Assimp

- [CVE-2022-45748](https://insights.sbomify.com/CVE-2022-45748/): Use after free in n/a (high 8.8)
- [CVE-2024-48423](https://insights.sbomify.com/CVE-2024-48423/): Use after free in n/a (high 8.4)
- [CVE-2024-45679](https://insights.sbomify.com/CVE-2024-45679/): Memory corruption in Assimp (high 8.4)
- [CVE-2024-40724](https://insights.sbomify.com/CVE-2024-40724/): Memory corruption in Assimp (high 8.4)
- [CVE-2022-38528](https://insights.sbomify.com/CVE-2022-38528/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3196 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 4 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3196 exists.

Affected packages and fixed versions:
- pyassimp (PyPI): affected all versions up to 5.4.3; no fix listed

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-3196/ (Markdown: https://insights.sbomify.com/CVE-2025-3196/index.md)
```

## Sources

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

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