RUSTSEC-2026-0579 json
The `Deque` implementation from `TryFrom` was wrong when the `Deque` ended up full
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
If the array passed to `Deque::try_from` was as long as the capacity of the `Deque`, it would lead to a invalid state.
Patch / fix
Is RUSTSEC-2026-0579 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 | 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.