Rust advisories / bitchomp
UnsoundRUSTSEC-2026-0131 · bitchomp
RUSTSEC-2026-0131: Double-free in `Chomp::inner()`
Short answerbitchomp has an API that can cause undefined behaviour from safe code: Double-free in `Chomp::inner()`. No fixed version yet.
| Crate | bitchomp |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2026-05-02 |
| Last changed | 2026-05-13 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i bitchomp. - Avoid the affected API, or replace the crate.
Details from the advisory
Chomp::inner() uses std::ptr::read_unaligned to move out the value from a raw pointer. If the original value is an owned type (e.g. Box), calling inner() moves out the ownership, but the original variable will still be dropped at the end of its scope. This causes the same heap memory to be freed twice, resulting in a double-free and undefined behavior.
This can be triggered through safe public APIs , Chomp::new() and Chomp::inner() , with no unsafe required from the caller.
References
- Package: crates.io/crates/bitchomp
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0131.html
- Report: github.com/KingPEPSALT/bitchomp/issues/5
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?