This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate futures_ringbuf

Dependencies

(6 total, 4 outdated, 1 insecure)

CrateRequiredLatestStatus
 futures^0.30.3.34up to date
 getrandom^0.20.4.3out of date
 log^0.40.4.35up to date
 rand^0.80.10.4out of date
 rand_chacha^0.30.10.0out of date
 ringbuf ⚠️^0.30.6.0insecure

Dev dependencies

(11 total, 1 outdated)

CrateRequiredLatestStatus
 assert_matches^11.5.0up to date
 async-std^11.13.2up to date
 asynchronous-codec^0.60.7.0out of date
 ergo-pin^0.10.1.0up to date
 futures-test^0.30.3.34up to date
 pretty_assertions^11.4.1up to date
 tokio^11.54.1up to date
 tokio-util^0.70.7.20up to date
 wasm-bindgen^0.20.2.130up to date
 wasm-bindgen-futures^0.40.4.80up to date
 wasm-bindgen-test^0.30.3.80up to date

Security Vulnerabilities

ringbuf: Double free / use-after-free in `Consumer::skip` and `Consumer::clear` when an element's `Drop` panics

RUSTSEC-2026-0293

Consumer::skip() and Consumer::clear() are not panic-safe. They drop the consumed elements in place and only afterwards call advance_read_index() to move the ring buffer's read index past them. If an element's Drop panics mid-loop, advance_read_index() is never reached, so the read index still points at the already-dropped elements. When the ring buffer is later dropped, its destructor re-visits those slots and drops the same elements a second time — a double free (CWE-415) / use-after-free (CWE-416) reachable from safe Rust, confirmed under AddressSanitizer.

Consumer::clear() delegates to Consumer::skip(self.len()), so both share the same root cause and the same fix.

Mitigation

Update to 0.5.2 or later (fixed in agerasev/ringbuf#60).