Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Informational severity, published 21 October 2026.

Which products and versions are affected?

tokio (crates.io) SEMVER:introduced=1.54.0,fixed=1.54.1; Tokio project Tokio 1.54.0.

Is there a fix for This vulnerability?

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 This vulnerability attacked?

It is attacked with local access, in a software library.

Check whether you run tokio (crates.io) or Tokio project 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.

Tokio race condition in Interval time driver

Severity: info · Published 2026-10-21

Tokio is an asynchronous runtime library for Rust applications. Version 1.54.0 contains a race condition in the Interval timer that can cause application crashes or memory corruption when using the multi-threaded runtime. This affects any application relying on Tokio's interval-based scheduling to trigger tasks repeatedly.

Technologies: tokio (crates.io). Vendors: crates.io.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Informational severity, published 21 October 2026.
Which products and versions are affected?: tokio (crates.io) SEMVER:introduced=1.54.0,fixed=1.54.1; Tokio project Tokio 1.54.0.
Is there a fix for This vulnerability?: 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 This vulnerability attacked?: It is attacked with local access, in a software library.
Am I affected?: Check whether you run tokio (crates.io) or Tokio project 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 Interval::poll_tick and the runtime's time driver thread in Tokio 1.54.0, allowing an internal timer entry to be dropped without proper synchronization. This results in a use-after-free vulnerability on the timer's waker and task state in safe Rust, potentially leading to assertion panics, reference-count corruption, or heap memory corruption. The vulnerability affects only Interval; Sleep and Timeout are unaffected. The bug is triggered on multi-threaded runtimes.

Affected products

Tokio project Tokio 1.54.0

Identifiers

GHSA-5wjr-9356-4wc8
RUSTSEC-2026-0384

Timeline

2026-10-21: disclosed
2026-10-21: patched: Version 1.54.0 yanked; fix released in 1.54.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.