CVE-2026-122330 · Package
NO FIX YET · SEE WHAT TO DO
Blosc c-blosc2 before 3.5.0 divides by zero when reading a slice of a crafted Blosc2 frame that has a zero chunksize or blocksize. An attacker who supplies such a frame crashes the process that reads it (SIGFPE).
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications that link c-blosc2 before 3.5.0 and open Blosc2 frames supplied from untrusted sources, such as uploaded or downloaded data files, can be crashed by a malicious frame. Programs that only read frames they created themselves, or that run in a trusted pipeline, are unlikely to be exposed. The sources do not say which downstream packages bundle c-blosc2.
Not affected if trusted-input-only, version-3.5.0-or-later
Who cares blosc2, c-blosc2, python
blosc2_version or the package manager listing, and see whether it is below 3.5.0.blosc2_schunk_open() or blosc2_schunk_from_buffer() on data from outside your control.3.5.0 (fixed version per the NVD description; the patch is linked from the sources)Blosc c-blosc2 before 3.5.0 contains a divide-by-zero vulnerability in blosc2_schunk_get_slice_buffer() in blosc/schunk.c that allows attackers to crash applications by supplying crafted frames with unchecked zero chunksize or blocksize values. Attackers can provide a malicious Blosc2 frame opened via blosc2_schunk_open() or blosc2_schunk_from_buffer() and read as a slice, raising SIGFPE and terminating the process.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.