OSV-2025-480
Stack-buffer-overflow in void glz::from<10000u, std::__1::__bit_reference<std::__1::vector<bool, std::__1
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=425725152
Crash type: Stack-buffer-overflow READ 1
Crash state:
void glz::from<10000u, std::__1::__bit_reference<std::__1::vector<bool, std::__1
void glz::from<10000u, std::__1::vector<bool, std::__1::allocator<bool>>>::op<gl
void glz::visit<4ul, void glz::from<10000u, my_struct>::op<glz::opts_csv{10000u,
What each source reports
OSV No score
Stack-buffer-overflow in void glz::from<10000u, std::__1::__bit_reference<std::__1::vector<bool, std::__1
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=425725152
Crash type: Stack-buffer-overflow READ 1
Crash state:
void glz::from<10000u, std::__1::__bit_reference<std::__1::vector<bool, std::__1
void glz::from<10000u, std::__1::vector<bool, std::__1::allocator<bool>>>::op<gl
void glz::visit<4ul, void glz::from<10000u, my_struct>::op<glz::opts_csv{10000u,
- Record
OSV-2025-480- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
glazeOSS-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-2025-480 is a vulnerability with no CVSS score yet in glaze, published June 20, 2025. No source lists public exploit code. A source reports a fix.