OSV-2026-1077
Heap-buffer-overflow in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
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
What each source reports
OSV No score
Heap-buffer-overflow in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
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
- Record
OSV-2026-1077- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
assimpOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2026-1077 is a vulnerability with no CVSS score yet in assimp, published July 28, 2026. No source lists public exploit code. No source names a fixed version.