Tokio reject_remote_clients configuration may get dropped when creating a Windows named pipe

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

EPSS

• CVE-2023-22466: 0.59% estimated exploitation activity in the next 30 days; percentile 48.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact When configuring a Windows named pipe server, setting pipemode will reset rejectremoteclients to false. If the application has previously configured rejectremoteclients to true, this effectively undoes the configuration. This also applies if rejectremoteclients is not explicitly set as this is the default configuration and is cleared by calling pipemode. Remote clients may only access the named pipe if the named pipe's associated path is accessible via a publically shared folder (SMB). Patches The following versions have been patched: 1.23.1 1.20.3 1.18.4 The fix will also be present in all releases starting from version 1.24.0. Named pipes were introduced to Tokio in version 1.7.0, so releases older than 1.7.0 are not affected. Workarounds Ensure that pipemode is set first after initializing a ServerOptions. For example: References https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea#piperejectremoteclients

Published by the source

6 Jan 2023, 21:40 UTC

Last modified by the source

3 Feb 2023, 05:01 UTC

Source last checked

26 Oct 2026, 15:33 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7rrj-xr53-82p7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-22466

Advisory: Tokio reject_remote_clients configuration may get dropped when creating a Windows named pipe
IDs: CVE-2023-22466, GHSA-7rrj-xr53-82p7
Record: https://patchnext.com/advisories/cve-2023-22466 (revision 1, source checked 26 Oct 2026, 15:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tokio 1.23.1, 1.20.3, 1.18.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io tokio: affected >= 1.7.0, < 1.18.4; >= 1.19.0, < 1.20.3; >= 1.21.0, < 1.23.1; fixed in 1.23.1, 1.20.3, 1.18.4

## Suggested inspection (read-only)
- crates.io tokio: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tokio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7rrj-xr53-82p7 (GitHub-reviewed advisory GHSA-7rrj-xr53-82p7 lists affected ranges: crates.io tokio >=1.7.0 =1.19.0 =1.21.0 <1.23.1)

Commands are suggestions: review each one before running it.