CVE-2026-133709 json
C-Blosc2 before 3.4.1 Heap Out-of-Bounds Read via frame_decompress_chunk
published yesterday modified yesterday also EUVD-2026-131538
- cvss
- 6.9
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
C-Blosc2 before 3.4.1 contains a heap-based out-of-bounds read vulnerability in frame_decompress_chunk() because sparse frame chunk cbytes are not checked against the actual chunk file size. Attackers can supply a sparse frame directory with a truncated or crafted chunk file to crash applications or leak adjacent heap memory into decompressed output.
Patch / fix
- Blosc c-blosc2 3.4.1
- github.com/Blosc/c-blosc2@b3fa6a2 commit
- github.com/Blosc/c-blosc2#822 pull request
- github.com/Blosc/c-blosc2/releases/tag/v3.4.1 release
Is CVE-2026-133709 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H |
Affected products
- Blosc c-blosc2
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/Blosc/c-blosc2/pull/822
issue-tracking, patch
-
github.com
/Blosc/c-blosc2/commit/b3fa6a2ab8eff77286ca295001d367efef56ca75
patch
-
github.com
/Blosc/c-blosc2/blob/v3.4.0/blosc/frame.c
technical-description
-
github.com
/Blosc/c-blosc2/releases/tag/v3.4.1
release-notes
-
vulncheck.com
/advisories/c-blosc2-before-3.4.1-heap-out-of-bounds-read-via-frame-decompress-chunk
third-party-advisory
Sources
- CVE List CVE-2026-133709
- NVD CVE-2026-133709
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.