Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Tokio versions 1.7.0 up to 1.18.4, 1.19.0 up to 1.20.3, and 1.21.0 up to 1.23.1 are affected. On Windows, calling pipe_mode on a named pipe ServerOptions silently sets reject_remote_clients to false, discarding any earlier explicit true setting, so remote clients may be allowed to connect. Upgrade to tokio 1.18.4, 1.20.3, or 1.23.1, depending on your release line. Until then, call pipe_mode before reject_remote_clients when configuring ServerOptions.
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 |
|---|---|---|---|---|
| 5.4 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0061, the 49th percentile, on 5 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
Sources
- GitHub Advisory Database: GHSA-7rrj-xr53-82p7
- OSV: GHSA-7rrj-xr53-82p7
- crates.io/crates/tokio
- rustsec.org/advisories/RUSTSEC-2023-0001.html
- github.com/tokio-rs/tokio/pull/5336
- github.com/tokio-rs/tokio/pull/5336
- learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea#pipe_reject_remote_clients