Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0577 json

Panicking `Drop` implementation could lead to UB

published 2d ago modified yesterday

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

Multiple functions dropped generic parameters but didn't properly handle the unwinding case, leading to broken invariants.

Reported by [tooson9010-spec](https://github.com/tooson9010-spec) and [Evian-Zhang](https://github.com/Evian-Zhang).

Patch / fix

  • crates.io heapless 0.9.4

Is RUSTSEC-2026-0577 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 heapless
>=0.0.0-0, <0.9.4
0.9.4

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.