Advisory

RUSTSEC-2026-0128

Also known as: None

Summary

Double-free and use-after-free in Keys::next()

Details

Keys::next() uses ptr::read to move out the Option<V> by value, which
drops the contained V when V is non-Copy (e.g. String). This leaves a
dangling value in the map's storage slot. Subsequent get() operations on
that key return a dangling reference to already-freed memory.

This can be triggered through safe public APIs — Map::keys(),
Keys::next(), and Map::get() — with no unsafe required from the
caller. Under Miri, accessing the freed slot produces "Undefined Behavior:
pointer not dereferenceable: alloc has been freed, so this pointer is
dangling".

Severity

Not rated by the source.

Dates

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

Affected packages and fixes

emap

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