Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Panic-safety unsoundness in `Stack::pop`, `Fifo::pop_front` and `Value::replace_stable` (use-after-free / double-free)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · RUSTSEC-2026-0272

Published

Three removal and replacement paths destroy an initialized value before committing the metadata change that removes it. Destruction runs `T::drop()`, which is user code and may panic. If it does, the commit is skipped and the container still claims ownership of the already-destroyed value, so its own destructor drops that value a second time. `Stack::pop` drops the top value before reducing `next_ofs`. `Stack`'s destructor pops in a loop, so an unchanged `next_ofs` re-drops the same value. `Fifo::pop_front` (via `pop_front_inner`) drops the front value before advancing `read_pos`. An unchanged `read_pos` still points at the destroyed value. `Value::replace_stable` drops the existing value before writing the replacement. If the destructor panics the replacement is never written, but the backing storage still holds the old value's metadata. This is separate from RUSTSEC-2021-0033, which covered a clone panic on insertion in `push_cloned` and was fixed in 0.6.1. ## Impact A heap-owning value is freed twice, corrupting the allocator. Reachable from safe Rust with any element type whose `Drop` can panic — no `unsafe` on the caller's side. * CWE-415 (Double Free) * CWE-416 (Use-After-Free) Confirmed under AddressSanitizer, which reports `attempting double-free` on all three paths. ## Fix Fixed in 0.8.2.

Source published
27 Aug 2026 12:00:00 UTC
Source modified
31 Aug 2026 09:45:02 UTC
Saved here
24 Oct 2026 13:19:54 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Nov 04:42 UTC · 272 of 275 readable · 268 fully read · documentation 469/469 current