Quick answers
- Is CVE-2026-115567 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115567 being exploited in the wild.
- How severe is CVE-2026-115567?
- Medium severity, with a CVSS score of 4, published 23 October 2026.
- Which products and versions are affected?
- tokio (crates.io) = 1.54.0, SEMVER:introduced=1.54.0,fixed=1.54.1; Tokio 1.54.0.
- Is there a fix for CVE-2026-115567?
- Yes. tokio (crates.io): upgrade to 1.54.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115567 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-115567?
- Check whether you run tokio (crates.io) or Tokio at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- tokio (crates.io): upgrade to 1.54.1 or later
cargo update -p tokio
Technical details
A race condition exists between tokio::time::Interval::poll_tick and the time driver's StateCell::fire, where dropping an elapsed timer entry without synchronizing with the driver thread creates a use-after-free on the timer's waker and task state. The vulnerability affects multi-threaded runtime configurations and manifests as unsafe memory access despite Rust's type system, leading to assertion failures or heap corruption.
Affected products
- Tokio Tokio 1.54.0
Identifiers
- CVE-2026-115567
- GHSA-5wjr-9356-4wc8
- RUSTSEC-2026-0384
Timeline
- 2026-10-23: disclosed
- 2026-10-21: patched: Revert fix committed before public disclosure