mio

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

1. High, CVSS 7.5crates.ioPublished 4 Mar 2024

   Mio's tokens for named pipes may be delivered after deregistration

   CVE-2024-27308 · GHSA-r8w9-5wcg-vfj7

   Affected

   • crates.io mio >= 0.7.2, <= 0.8.10

   Fixed in

   0.8.11· Vendor fix available

   Issue

   Impact When using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free. For users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio. The vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected. Affected versions This vulnerability has been fixed in mio v0.8.11. All versions of mio between v0.7.2 and v0.8.10 are vulnerable. Tokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not…

   Recommended action: Upgrade to 0.8.11 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

   Sources:github.comSource checked 26 Oct 2026, 15:42 UTCEvidence →
2. Medium, CVSS 5.5crates.ioPublished 25 Aug 2021

   mio invalidly assumes the memory layout of std::net::SocketAddr

   CVE-2020-35922 · GHSA-pf3p-x6qj-6j7q

   Affected

   • crates.io mio >= 0.7.0, < 0.7.6

   Fixed in

   0.7.6· Vendor fix available

   Issue

   The mio crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.

   Recommended action: Upgrade to 0.7.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

   Sources:github.comSource checked 26 Oct 2026, 15:34 UTCEvidence →