# Panic-safety unsoundness in \`BitVecCore::clear\` (double-free / use-after-free) Advisory record · `GHSA-mr2v-63pc-gmr4` - **Identifiers:** `GHSA-mr2v-63pc-gmr4` · `RUSTSEC-2026-0267` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **Published:** 24 Aug 2026 - **Updated:** 25 Aug 2026 - **Reviewed by a person:** No 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. ## Affected packages - `stable-vec` (crates.io): affected `>=0.0.0-0, <0.4.3`; fixed in `0.4.3` ## 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 - 31 Oct 2026, 15:18 UTC: First seen by agentprime - 31 Oct 2026, 15:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0267) ## Sources - [GitHub Advisory Database: GHSA-mr2v-63pc-gmr4](https://github.com/advisories/GHSA-mr2v-63pc-gmr4) - [OSV: GHSA-mr2v-63pc-gmr4](https://osv.dev/vulnerability/GHSA-mr2v-63pc-gmr4) - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .