OSV-2021-593
Heap-use-after-free in std::__1::vector<char, std::__1::allocator<char> >::size
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32822
Crash type: Heap-use-after-free READ 8
Crash state:
std::__1::vector<char, std::__1::allocator<char> >::size
std::__1::vector<char, std::__1::allocator<char> >::resize
Assimp::TXmlParser<pugi::xml_node>::clear
What each source reports
OSV No score
Heap-use-after-free in std::__1::vector<char, std::__1::allocator<char> >::size
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32822
Crash type: Heap-use-after-free READ 8
Crash state:
std::__1::vector<char, std::__1::allocator<char> >::size
std::__1::vector<char, std::__1::allocator<char> >::resize
Assimp::TXmlParser<pugi::xml_node>::clear
- Record
OSV-2021-593- 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-2021-593 is a vulnerability with no CVSS score yet in assimp, published April 3, 2021. No source lists public exploit code. A source reports a fix.