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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | 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