C-Blosc2 out-of-bounds read in frame_decompress_chunk
- Exploited
- No known exploitation
- Fix
- Fixed in 3.4.1
- Who is exposed
- Not reported
Summary
C-Blosc2 has a heap out-of-bounds read in frame_decompress_chunk() that can crash applications or leak nearby heap memory into decompressed output. A local attacker with no login can supply a crafted sparse frame with a truncated or manipulated chunk file, and a user must take an action for the attack to proceed.
Written by a model
Original description
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.
What to do
Upgrade to a fixed version: 3.4.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133709 (C-Blosc2 before 3.4.1 Heap Out-of-Bounds Read via frame_decompress_chunk), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133709 (entry last updated 2026-11-20):
Affected:
- Blosc c-blosc2: fixed in 3.4.1
Fixed versions: 3.4.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133709 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133709 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Blosc/c-blosc2/pull/822
- https://github.com/Blosc/c-blosc2/commit/b3fa6a2ab8eff77286ca295001d367efef56ca75
- https://github.com/Blosc/c-blosc2/blob/v3.4.0/blosc/frame.c
- https://github.com/Blosc/c-blosc2/releases/tag/v3.4.1
- https://www.vulncheck.com/advisories/c-blosc2-before-3.4.1-heap-out-of-bounds-read-via-frame-decompress-chunk
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133709
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133709"}.Affected versions
- Blosc c-blosc2fixed in 3.4.1
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133709 |
| Record | NVD · CVE-2026-133709 |
| Other links 5 | |
| Patch | GitHub · Blosc/c-blosc2 · Pull request #822 |
| Patch | GitHub · Blosc/c-blosc2 · Commit b3fa6a2a |
| Repository | GitHub · Blosc/c-blosc2 · blosc/frame.c |
| Repository | GitHub · Blosc/c-blosc2 · Release v3.4.1 |
| Link | vulncheck.com · advisories/c-blosc2-before-3.4.1-heap-out-of-bounds-read-via-frame-decompress-chunk |
Questions about CVE-2026-133709
Is CVE-2026-133709 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133709?
c-blosc2: before 3.4.1.
Source: cve.now feed data
How do I fix CVE-2026-133709?
Upgrade to a fixed version: 3.4.1.
Source: cve.now feed data
Related
- CVE-2026-122330Blosc c-blosc2 before 3.5.0 Divide-by-Zero via blosc2_schunk_get_slice_buffer()
- CVE-2026-103222Blosc C-Blosc2 blosclz Decompression blosclz.c blosclz_decompress integer overflow
- CVE-2026-77347Pozeiden: Out-of-bounds read/write (crash / memory corruption) on valid diagrams in grid-layout renderers
- CVE-2026-130151FreeRDP Smartcard Redirection Memory Handling in Okta Privileged Access Gateway
- CVE-2026-49388Netatalk: Heap out-of-bounds read in afpd Spotlight RPC unmarshalling via unbounded toc_index in sl_unpack_loop()
- CVE-2026-49387Netatalk: Heap out-of-bounds read in afpd Spotlight RPC unmarshalling via unbounded element count in sl_unpack_ints() and sibling handlers
No corrections so far. Something wrong on this page? Report an error.