- 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
`DCtx::try_clone` (`experimental` feature, deprecated) is a plain copy of the C context. A context owning a dictionary (from `load_dictionary`, `ref_prefix` or `init_using_dict`) or a dictionary table (`ref_ddict` with `RefMultipleDDicts`) ended up with both copies freeing it. A context cloned mid-frame resumed on uninitialized stream state. The clone also silently lost the `WindowLogMax` limit.
The flaw was corrected by refusing to clone such contexts, and by carrying over the parameters the copy leaves out.
Patch / fix
- crates.io zstd-safe 7.4.0, 8.2.0
- github.com/gyscos/zstd-rs@cee6529 commit
- github.com/gyscos/zstd-rs#384 pull request
Is RUSTSEC-2026-0404 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | zstd-safe | >=4.1.4, <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.