RUSTSEC-2026-0131 Double-free in `Chomp::inner()`
A double-free vulnerability in the Chomp library allows attackers to trigger undefined behavior, potentially leading to code execution or crashes via safe public APIs.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is RUSTSEC-2026-0131?
RUSTSEC-2026-0131 is an use after free vulnerability in bitchomp, published on 2 May 2026.
Official description
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.
Which versions are affected by RUSTSEC-2026-0131?
1 open source package ship an affected version, including bitchomp.
| Package | Affected | Fixed in |
|---|---|---|
bitchomp crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2026-0131?
No fix has been published for RUSTSEC-2026-0131 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is RUSTSEC-2026-0131 being exploited?
There is no known exploitation of RUSTSEC-2026-0131 in the wild and no public exploit code.