# CVE-2025-11275: Open Asset Import Library Assimp OpenDDLParserUtils.h getNextSeparator heap-based overflow

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

- **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:** No
- **Published:** 5 Oct 2025
- **Updated:** 24 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-11275, GHSA-vxpx-mqx4-f9h3, PYSEC-2025-156, UBUNTU-CVE-2025-11275

## What is CVE-2025-11275?

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

### Official description

A vulnerability was identified in Open Asset Import Library Assimp 6.0.2. Affected by this vulnerability is the function ODDLParser::getNextSeparator in the library assimp/contrib/openddlparser/include/openddlparser/OpenDDLParserUtils.h. Such manipulation leads to heap-based buffer overflow. The attack must be carried out locally. The exploit is publicly available and might be used.

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-11275?

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


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

Products: Assimp Assimp.

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

No fix has been published for CVE-2025-11275 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11275 being exploited?

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

What it is: CVE-2025-11275 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 5 Oct 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-11275 exists.

Affected packages and fixed versions:
- pyassimp (PyPI): affected all versions up to 6.0.2; 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-11275/ (Markdown: https://insights.sbomify.com/CVE-2025-11275/index.md)
```

## Sources

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

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