Skip to main content
No exploitation reportedFix available

CVE-2023-22466

No exploitation reported by the sources we read.

  • Published2023-01-04
  • Fixed in1.23.1 · 1.20.3 · 1.18.4
  • WeaknessCWE-665

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Tokio is a runtime for writing applications with Rust. Starting with version 1.7.0 and prior to versions 1.18.4, 1.20.3, and 1.23.1, when configuring a Windows named pipe server, setting `pipe_mode` will reset `reject_remote_clients` to `false`. If the application has previously configured `reject_remote_clients` to `true`, this effectively undoes the configuration. Remote clients may only access the named pipe if the named pipe's associated path is accessible via a publicly shared folder (SMB). Versions 1.23.1, 1.20.3, and 1.18.4 have been patched. 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. As a workaround, ensure that `pipe_mode` is set first after initializing a `ServerOptions`.

Timeline

dates in UTC
  1. 2023-01-0422:15CVE publishedNVD

Versions per branch

NVD · OSV
Tokio
BranchAffectedFixed in
1.x≥ 1.21.0, < 1.23.11.23.1
1.x≥ 1.19.0, < 1.20.31.20.3
1.x≥ 1.7.0, < 1.18.41.18.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • tokio-rs tokio
    Affected
    • = >= 1.7.0, < 1.18.4no fix stated
    • = >= 1.19.0, < 1.20.3no fix stated
    • = >= 1.21.0, < 1.23.1no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-01-04

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • pulumi-watchWolfiall versions · fixed in 0.1.5-r5
  • pulumi-watchChainguardall versions · fixed in 0.1.5-r5
  • rust-tokioUbuntu:22.04:LTSall versions · no fixed version listed
  • rust-tokioDebian:14all versions · fixed in 1.24.2-1
  • rust-tokioDebian:13all versions · fixed in 1.24.2-1
  • rust-tokioDebian:12all versions · fixed in 1.24.2-1

Full record on NVD

Fix

  1. Update Tokio to 1.23.1 · 1.20.3 · 1.18.4

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2025-03-10
  • CNACVSS 3.15.4known since 2026-10-23
  • NVDCVSS 3.15.4read 2026-10-23
  • CNAweakness (CWE)CWE-665known since 2026-10-23
  • FIRST EPSSEPSS score0.6 %2026-11-09
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2023-01-06

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Published
2023-01-04
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-7rrj-xr53-82p7

Frequently asked questions

What is CVE-2023-22466?

Tokio is a runtime for writing applications with Rust. Starting with version 1.7.0 and prior to versions 1.18.4, 1.20.3, and 1.23.1, when configuring a Windows named pipe server, setting `pipe_mode` will reset `reject_remote_clients` to `false`. If the application has previously configured `reject_remote_clients` to `true`, this effectively undoes the configuration. Remote clients may only access the named pipe if the named pipe's associated path is accessible via a publicly shared folder (SMB). Versions 1.23.1, 1.20.3, and 1.18.4 have been patched. 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. As a workaround, ensure that `pipe_mode` is set first after initializing a `ServerOptions`.

Is CVE-2023-22466 actively exploited?

Active exploitation of CVE-2023-22466 has not been confirmed. Its EPSS score was 0.6% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-22466?

CVE-2023-22466 has a CVSS v3 base score of 5.4 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N.

Running tokio? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record