Advisory

RUSTSEC-2026-0131

Also known as: None

Summary

Double-free in Chomp::inner()

Details

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.

Severity

Not rated by the source.

Dates

Published
2026-05-02 12:00 UTC
Modified
2026-05-13 12:45 UTC

Affected packages and fixes

bitchomp

crates.io · All systems

Affected

  • introduced 0.0.0-0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

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