ZDF
Sign inSign up

Vulnerabilities

Vulnerability · RUSTSEC-2026-0408

Aliasing violations in splice, mutable iteration and cursors

Published Oct 24, 2026 · catalog updated Oct 26, 2026 · RustSec Rust

Last checked Oct 27, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2026-0408. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.

Same product and reporting

Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
crates.io skiplist

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 types. 1. **Splice back-pointer.** , and stored the first spliced node's pointer from a reference to the head, then wrote through that same reference, invalidating the stored pointer. A later or writes through it. This affects all four collections. 2. ** back pointer.** With an or upper bound, the back pointer came from a shared reference. hands out through it, and writing to that value is undefined behaviour. 3. ** reads a yielded node.** In and , read the predecessor node even after the front end had yielded it as . The read freezes the caller's reference, and the caller's next write through it is undefined behaviour. This affects , and used from both ends. 4. **Cursor list pointer.** and on and ( feature) took the cursor's list pointer, then searched through . A comparator with interior-mutable state, such as a 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. 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • crates.io skiplist0.0.0-0 → 1.3.0

How to fix RUSTSEC-2026-0408

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for RUSTSEC-2026-0408. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0.0.0-0 → 1.3.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 24, 2026 · GitHub Advisory Database

    Detected

    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 types. 1. **Splice back-pointer.** , and stored the first spliced node's pointer from a reference to the head, then wrote through that same r

  2. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    skiplist fixed in 1.3.0

  3. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    skiplist fixed in 1.3.0

  4. Oct 26, 2026 · GitHub Advisory Database

    Updated

    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 types. 1. **Splice back-pointer.** , and stored the first spliced node's pointer from a reference to the head, then wrote through that same r

Sources

  • GitHub Advisory DatabasePackage advisoryGHSA-924w-mwc9-86m8

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • OpenSSF OSV / OSV ScannerPackage advisoryRUSTSEC-2026-0408

    Aliasing violations in splice, mutable iteration and cursors

    osv.dev
  • RustSec Advisory DBVendor advisoryRUSTSEC-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 types. 1. **Splice ba

    crates.io

References

Freshness

Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • RustSec Advisory DBOct 27, 2026
  • GitHub Advisory DatabaseOct 26, 2026
  • OpenSSF OSV / OSV ScannerOct 26, 2026