PT-2026-40738 · Crates.Io · Bitchomp

Published

2026-05-02

·

Updated

2026-05-02

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

RUSTSEC-2026-0131

Affected Products

Bitchomp