Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
RUSTSEC-2026-0128
No affected components available
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".
Measures severity based on intrinsic characteristics of the vulnerability, independent of environment.
No exploitation activity has been observed at this time. Continue routine monitoring.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard