Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-mr2v-63pc-gmr4

Panic-safety unsoundness in `BitVecCore::clear` (double-free / use-after-free)

No CVSS score

Published by the GitHub Advisory Database at 24 Aug 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
stable-veccrates.io>=0.0.0-0, <0.4.30.4.3
Identifiers
GHSA-mr2v-63pc-gmr4 · RUSTSEC-2026-0267
Published
24 Aug 2026
Updated
25 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The stable-vec crate, versions before 0.4.3, has a panic-safety bug in its clear operation. If an element's Drop implementation panics during clear, the slot of that element is left marked as occupied, so it is dropped a second time when the vector is dropped, causing a double free and use-after-free. An attacker needs only to use safe Rust with an element type whose Drop can panic, reached through StableVec::clear or ExternStableVec::clear. Upgrade to stable-vec 0.4.3, which fixes the issue.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:18 UTC First seen by agentprime
  2. 31 Oct 2026, 15:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.