OSV-2021-464

Heap-buffer-overflow in blosc_read_header

No scoreFix available

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31535

Crash type: Heap-buffer-overflow READ 16
Crash state:
blosc_read_header
blosc2_cbuffer_sizes
frame_get_lazychunk

What each source reports

OSV No score

Heap-buffer-overflow in blosc_read_header

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31535

Crash type: Heap-buffer-overflow READ 16
Crash state:
blosc_read_header
blosc2_cbuffer_sizes
frame_get_lazychunk

Record: OSV-2021-464
Updated: 2026-11-02

Affected packages

Affected packages
Package	Affected	Fixed
`c-blosc2` OSS-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

History
Recorded	Changed	Sources
Nov 2, 2026	first indexed	OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

OSV-2021-464 is a vulnerability with no CVSS score yet in c-blosc2, published March 1, 2021. No source lists public exploit code. A source reports a fix.

References

bugs.chromium.org/p/oss-fuzz/issues/detail?id=31535