cve.bz

CVE-2026-115567 tokio-rs tokio: Race Condition

5.8 mediumEPSS 0.1%Fix available

Medium (5.8) in tokio-rs tokio. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in tokio 1.54.1.

On this page
Tokio is a runtime for writing applications with Rust. In 1.54.0, a race condition between tokio::time::Interval::poll_tick (including .tick().await) and the multi-threaded runtime's time driver could drop an internal timer entry without synchronizing with the driver thread that was firing it. The race caused a use-after-free on the timer's waker and task state in safe Rust, which could produce assertion panics, task reference-count corruption, or heap memory corruption. This issue is fixed in 1.54.1.

Severity

CVSS 4.0

5.8 medium
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • tokio (crates.io): fixed in 1.54.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-115567 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115567?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115567?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115567 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
tokio-rs tokio= 1.54.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5wjr-9356-4wc8crates.iotokio>=1.54.0 <1.54.11.54.1
RUSTSEC-2026-0384crates.iotokio>=1.54.0 <1.54.11.54.1

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploitation requires winning a narrow race condition locally against multi-threaded runtime services, primarily resulting in process crashes or denial of service rather than arbitrary code execution. Tokio provides an asynchronous execution framework that is statically embedded within select system and container management utilities across Red Hat products. Exploiting this flaw necessitates local user access and precise timing during interval timer operations on multi-threaded runtimes, substantially limiting attacker reliability and operational blast radius.

ProductPackageStateAdvisory
Ansible Automation Orchestrator 2026ansible-automation-platform/automation-orchestrator-backend-rhel9Fix deferred
Confidential Cluster Operatorconfidential-clusters-beta/attestation-key-register-rhel9Fix deferred
Confidential Cluster Operatorconfidential-clusters-beta/compute-pcrs-rhel9Fix deferred
Confidential Cluster Operatorconfidential-clusters-beta/confidential-cluster-operator-bundleFix deferred
Confidential Cluster Operatorconfidential-clusters-beta/confidential-cluster-rhel9-operatorFix deferred
Confidential Cluster Operatorconfidential-clusters-beta/registration-server-rhel9Fix deferred
Confidential Compute Attestationbuild-of-trustee/trustee-rhel9Fix deferred
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-payload-rhel9Fix deferred
Lightspeed Services for Advanced Cluster Managementlightspeed-services-acm/ocp-rules-rhel9Fix deferred
Logging Subsystem for Red Hat OpenShiftopenshift-logging/vector-rhel9Out of support scope
OpenShift Lightspeedopenshift-lightspeed/lightspeed-ocp-rag-rhel9Fix deferred
OpenShift Service Mesh 3openshift-service-mesh/istio-ztunnel-rhel9Fix deferred
Red Hat Advanced Cluster Security 4advanced-cluster-security/rhacs-fact-rhel8Fix deferred
Red Hat Advanced Cluster Security 4advanced-cluster-security/rhacs-fact-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-chatbot-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/hub-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/lightspeed-chatbot-rhel9Fix deferred
Red Hat Connectivity Link 1rhcl-1/limitador-rhel9Fix deferred
Red Hat Connectivity Link 1rhcl-1/wasm-shim-rhel9Fix deferred
95 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-115567.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON