RUSTSEC-2026-0576: `IndexMap::truncate` could lead to an inconsistent state
Published Nov 18, 2026
·Updated
IndexMap::truncate was not rebuilding indices when it should, leading to an inconsistent state and memory corruption.
Reported by Jacob Finkelman.
Affected Software
1 affected componentFixes available
rust/heapless>=0.0.0-0<0.9.4
0.9.4
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rust/heaplessto a version that resolves this vulnerability.Fixed in 0.9.4
Event History
Nov 18, 2026
Advisory Published
via OSV·12:00 PM
Data Sourced
via OSV·12:00 PM
DescriptionAffected Software
Frequently Asked Questions
1
What operations could leave an IndexMap in the vulnerable inconsistent state?
Calling IndexMap::truncate can leave its indices unreconstructed when they should be rebuilt, producing an inconsistent state that can lead to memory corruption.
2
What impact is documented if this issue is triggered?
The documented impact is memory corruption following the inconsistent IndexMap state.