# CVE-2025-2592: Open Asset Import Library Assimp CSMLoader.cpp InternReadFile heap-based overflow

> A heap-based buffer overflow in Assimp's CSMLoader allows remote attackers to execute arbitrary code or cause denial of service via crafted files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Mar 2025
- **Updated:** 21 Mar 2025
- **Also known as:** DEBIAN-CVE-2025-2592, GHSA-gq4x-2qp9-2gvw, PYSEC-2025-260, UBUNTU-CVE-2025-2592, openSUSE-SU-2025:0117-1

## What is CVE-2025-2592?

CVE-2025-2592 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 21 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as critical, has been found in Open Asset Import Library Assimp 5.4.3. This issue affects the function CSMImporter::InternReadFile of the file code/AssetLib/CSM/CSMLoader.cpp. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The patch is named 2690e354da0c681db000cfd892a55226788f2743. It is recommended to apply a patch to fix this issue.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

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 |
| `doomsday` | SUSE:Package Hub 15 SP6 | All versions | 2.3.1-bp156.4.3.1 |
| `doomsday` | openSUSE:Leap 15.6 | All versions | 2.3.1-bp156.4.3.1 |

Products: Assimp Assimp.

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

Apply the vendor's patch.

## Is CVE-2025-2592 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2592 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-2592 and fix it if it is affected.

What it is: CVE-2025-2592 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 21 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2592 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-2592/ (Markdown: https://insights.sbomify.com/CVE-2025-2592/index.md)
```

## Sources

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

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