OSV-2026-1077 Heap-buffer-overflow in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
A heap-buffer-overflow in the Assimp library's XFile parser allows attackers to cause denial of service or potentially execute code via crafted files.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is OSV-2026-1077?
OSV-2026-1077 is a memory corruption vulnerability in assimp, published on 28 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=536937906
Crash type: Heap-buffer-overflow READ {*}
Crash state:
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
Assimp::XFileParser::GetNextToken
Assimp::XFileParser::ParseDataObjectTemplate
Which versions are affected by OSV-2026-1077?
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-1077?
No fix has been published for OSV-2026-1077 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-1077 being exploited?
There is no known exploitation of OSV-2026-1077 in the wild and no public exploit code.