Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0528 json

UB can be reached from safe code

published yesterday modified 10h 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

The variance of `RefSwap` and `OptionRefSwap` were incorrect, possibly allowing use-after-free.

`OptionRefSwap::into_inner` did not check for null.

The fix is to make `RefSwap` and `OptionRefSwap` invariant, and to change `OptionRefSwap::into_inner` to return an option. It is available in version 0.1.3. If your project still compiles with 0.1.3 then it is not affected by the unsoundness on version 0.1.2

Patch / fix

  • crates.io ref-swap 0.1.3

Is RUSTSEC-2026-0528 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 ref-swap
>=0.0.0-0, <0.1.3
0.1.3

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.