# Tokens for named pipes may be delivered after deregistration Advisory record · `GHSA-r8w9-5wcg-vfj7` - **Identifiers:** `GHSA-r8w9-5wcg-vfj7` · `CVE-2024-27308` · `RUSTSEC-2024-0019` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html) · [CWE-672](https://cwe.mitre.org/data/definitions/672.html) - **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [CWE-672](https://agentprime.io/advisories/tag/cwe-672.md) - **Published:** 4 Mar 2024 - **Updated:** 12 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 4 Mar 2024, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `mio` (crates.io): affected `>=0.7.2, <0.8.11`; fixed in `0.8.11` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Mio versions from 0.7.2 up to but not including 0.8.11 are affected, and the fix is in 0.8.11, so upgrade to mio 0.8.11 or later. On Windows, when named pipes are used, mio may deliver a token for a pipe that was already deregistered, which can lead to a use-after-free in applications that store pointers in tokens, including Tokio users on Tokio 1.30.0 or later. The source gives no workaround beyond having affected libraries detect and ignore invalid tokens. Written 3 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 - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0088, the 59th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:24 UTC: First seen by agentprime - 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2024-0019) ## Sources - [GitHub Advisory Database: GHSA-r8w9-5wcg-vfj7](https://github.com/advisories/GHSA-r8w9-5wcg-vfj7) - [OSV: GHSA-r8w9-5wcg-vfj7](https://osv.dev/vulnerability/GHSA-r8w9-5wcg-vfj7) - - - 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: .