RUSTSEC-2026-0580: The treiber stack implementation in heapless had a race condition
Published Nov 18, 2026
·Updated
In the affected versions, it was possible for two threads or execution contexts running concurrently to race, causing one to read out of a pointer that had been invalidated by another execution context.
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 conditions are required to trigger the issue?
Two threads or execution contexts must access the treiber stack implementation concurrently. The race can cause one context to read through a pointer that another context has invalidated.
2
What is the potential impact of a successful race?
A successful race results in an out-of-pointer read involving an invalidated pointer. The provided information does not specify further consequences or affected version ranges.