Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
RUSTSEC-2026-0408
Four code paths create a pointer whose permission is later revoked, then
write through it. Miri reports each as undefined behaviour under both the
Tree Borrows and Stacked Borrows aliasing models (CWE-758). All four are
reachable from safe code with standard Ord types.
- Splice back-pointer.
split_off,split_off_indexandappendstored the first spliced node'sprevpointer from a reference to the head, then wrote through that same reference, invalidating the stored pointer. A laterpop_firstorpop_frontwrites through it. This affects all four collections. SkipMap::range_mutback pointer. With anIncludedorExcludedupper bound, the back pointer came from a shared reference.next_backhands out&mut Vthrough it, and writing to that value is undefined behaviour.IterMut::next_backreads a yielded node. InSkipListandSkipMap,next_backread the predecessor node even after the front end had yielded it as&mut. The read freezes the caller's reference, and the caller's next write through it is undefined behaviour. This affectsiter_mut,values_mutandrange_mutused from both ends.- Cursor list pointer.
lower_bound_mutandupper_bound_mutonOrderedSkipListandSkipSet(cursorfeature) took the cursor's list pointer, then searched through&self. A comparator with interior-mutable state, such as aCellcall counter, wrote to the list's memory through that shared borrow and invalidated the cursor's pointer. The comparator can be a fully consistent order.SkipMapcursors are not affected.
No miscompilation has been observed in an optimised build. A future compiler may still optimise on the violated aliasing assumptions.
The flaws were corrected in 1.3.0. Each fix derives the pointer used for mutation from the collection's long-lived allocation pointers, and each has a Miri regression test.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability.
Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard