OSV-2026-1049 Heap-buffer-overflow in Assimp::X3DExporter::CheckAndExport_Light
Not scored
Published
Check this codebase for OSV-2026-1049 and fix it if it is affected.
What it is: OSV-2026-1049 is a memory corruption vulnerability in assimp, published on 10 Jul 2026.
Exploitation: There is no known exploitation of OSV-2026-1049 in the wild and no public exploit code.
Affected packages and fixed versions:
- assimp (OSS-Fuzz): affected all versions; 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/OSV-2026-1049/ (Markdown: https://insights.sbomify.com/OSV-2026-1049/index.md)
A heap-buffer-overflow in the Assimp library's X3D exporter can cause a crash when processing malicious 3D model files.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is OSV-2026-1049?
OSV-2026-1049 is a memory corruption vulnerability in assimp, published on 10 Jul 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=532625491
Crash type: Heap-buffer-overflow READ 8
Crash state:
Assimp::X3DExporter::CheckAndExport_Light
Assimp::X3DExporter::Export_Node
Assimp::X3DExporter::X3DExporter
Which versions are affected by OSV-2026-1049?
1 open source package ship an affected version, including assimp.
| Package | Affected | Fixed in |
|---|---|---|
assimp OSS-Fuzz | All versions | None |
How do I fix OSV-2026-1049?
No fix has been published for OSV-2026-1049 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is OSV-2026-1049 being exploited?
There is no known exploitation of OSV-2026-1049 in the wild and no public exploit code.