Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0396 json

`Seekable` reads a NULL or out-of-bounds seek table

published 26d ago modified 10d ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

`Seekable` did not record whether it was initialized. On a fresh `Seekable`, or one whose `init_buff()` failed, `decompress`, `offset_to_frame_index` and `frame_decompressed_size` made the C library read a NULL seek table. After a failed re-initialization, `decompress` returned data from the refused buffer using the previous seek table.

Separately, `frame_decompressed_size(num_frames())`, on `Seekable` and `SeekTable`, read one entry past the end of the seek table.

The flaw was corrected by refusing to use a `Seekable` until an initialization succeeded, and by checking the frame index.

Patch / fix

  • crates.io zstd-safe 7.4.0, 8.2.0

Is RUSTSEC-2026-0396 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io zstd-safe
>=7.2.2, <7.4.0
>=8.0.0-0, <8.2.0
7.4.0
8.2.0

References

Sources

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.