CVE-2026-115567
Published:October 23, 2026
Updated:October 29, 2026
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.
Affected Packages
https://github.com/tokio-rs/tokio.git (GITHUB):
Affected version(s) =tokio-1.54.0 <tokio-1.54.1Fix Suggestion:
Update to version tokio-1.54.1tokio (RUST):
Affected version(s) =1.54.0 <1.54.1Fix Suggestion:
Update to version 1.54.1Related Resources (10)
Do you need more information?
Contact UsCVSS v4
Base Score:
5.8
Attack Vector
LOCAL
Attack Complexity
HIGH
Attack Requirements
PRESENT
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
LOW
Vulnerable System Availability
HIGH
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.3
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
HIGH
Weakness Type (CWE)
Concurrent Execution using Shared Resource with Improper Synchronization
EPSS
Base Score:
0.11