Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of the skiplist crate before 1.3.0 can free a node that is still linked when a Comparator or Ord implementation gives inconsistent answers for the same pair of values during one mutating call, such as insert, take_first, take or remove. A later call then reads the freed memory. No unsafe code is needed: a safe Ord implementation with the default comparator can trigger it, but only if the comparison is stateful or non-deterministic. Upgrade to skiplist 1.3.0 or later, where such contradictions cause a panic before the collection is modified.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| Not published | None | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N | OSV |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV