Advisory

RUSTSEC-2026-0298

Also known as: GHSA-8gw6-724c-9h38

Summary

Use-after-free when a future's Drop panics while the container is dropped

Details

Storage::clear walks the slab, empties each entry and frees the Task
allocation once its reference count reaches zero. self.tasks.set_len(0) only
runs after the loop.

Emptying an entry drops the user future it holds, and T carries no bounds
excluding a panicking Drop. If one unwinds, the length is never committed and
self.tasks still holds the pointers already processed. Drop for Storage
calls clear again, and the second pass dereferences (*task.as_ptr()).entry
on allocations the first pass already freed — a use-after-free (CWE-416)
reachable from safe Rust.

Storage is reached only through Unordered, whose Drop calls clear. No
particular method call is needed; dropping the container is enough.

Mitigation

Update to 0.10.3.

Severity

Not rated by the source.

Dates

Published
2026-09-12 12:00 UTC
Modified
2026-09-22 07:45 UTC

Affected packages and fixes

unicycle

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.10.3 (semver)

Fixed versions

0.10.3

Fix

  • Fixed version 0.10.3
    cargo update -p unicycle --precise 0.10.3

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences