Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0399 json

Use-after-free through `init_using_cdict` and `init_using_ddict`

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

`CCtx::init_using_cdict` and `DCtx::init_using_ddict` (`experimental` feature, deprecated) took the dictionary as `&CDict<'b>` and `&DDict<'b>` with only `'b: 'a`, so the dictionary itself could be dropped while the context still pointed at it. The same mistake in other constructors was fixed earlier (<https://github.com/gyscos/zstd-rs/issues/365>).

The flaw was corrected by taking `&'a CDict<'b>` and `&'a DDict<'b>`.

Patch / fix

  • crates.io zstd-safe 7.4.0, 8.2.0

Is RUSTSEC-2026-0399 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
>=3.0.0, <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.