ZDF
Sign inSign up

Vulnerabilities

Vulnerability · RUSTSEC-2026-0384

Race condition in on Tokio v1.54.0

Published Oct 21, 2026 · catalog updated Oct 22, 2026 · RustSec Rust

Last checked Oct 23, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2026-0384. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.

Same product and reporting

Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
crates.io tokio

## Summary On the multi-threaded runtime, there is a race condition between and the runtime's time driver. This affects only. and are **not** affected. ## Details In Tokio v1.54.0, a race condition between (including ) and the runtime time driver can drop an internal timer entry without synchronizing with the driver thread that is firing it. This causes a data race and use-after-free on the timer's waker and task state in safe Rust, leading to assertion panics, task reference-count corruption, or heap memory corruption. This bug was introduced by https://github.com/tokio-rs/tokio/pull/8458, and it was fixed by https://github.com/tokio-rs/tokio/pull/8692. ## Impact This may lead to crashes and use-after-frees in applications using on a multi-threaded runtime. Since this issue is known to lead to crashes in production systems, the v1.54.0 release of Tokio has been yanked. ## Credits Thank you to [creepycode](https://github.com/ByteZ1337) and [carabistouille](https://github.com/carabistouflette) for reporting this privately using the procedure outlined in our security policy. They both reported the issue independently of each other.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • crates.io tokio1.54.0 → 1.54.1

How to fix RUSTSEC-2026-0384

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for RUSTSEC-2026-0384. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 1.54.0 → 1.54.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 21, 2026 · GitHub Advisory Database

    Detected

    ## Summary On the multi-threaded runtime, there is a race condition between and the runtime's time driver. This affects only. and are **not** affected. ## Details In Tokio v1.54.0, a race condition between (including ) and the runtime time driver can drop an internal timer entry without synchronizing with the driver thread that is firing it. This causes a data race and use-after-free on the timer'

  2. Oct 22, 2026 · GitHub Advisory Database

    Fix available

    tokio fixed in 1.54.1

  3. Oct 22, 2026 · GitHub Advisory Database

    Fix available

    tokio fixed in 1.54.1

  4. Oct 22, 2026 · GitHub Advisory Database

    Updated

    ## Summary On the multi-threaded runtime, there is a race condition between and the runtime's time driver. This affects only. and are **not** affected. ## Details In Tokio v1.54.0, a race condition between (including ) and the runtime time driver can drop an internal timer entry without synchronizing with the driver thread that is firing it. This causes a data race and use-after-free on the timer'

Sources

  • GitHub Advisory DatabasePackage advisoryGHSA-5wjr-9356-4wc8

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • OpenSSF OSV / OSV ScannerPackage advisoryRUSTSEC-2026-0384

    Race condition in on Tokio v1.54.0

    osv.dev
  • RustSec Advisory DBVendor advisoryRUSTSEC-2026-0384

    ## Summary On the multi-threaded runtime, there is a race condition between and the runtime's time driver. This affects only. and are **not** affected. ## Details In Tokio v1.54.0, a race condition between (including ) and the runtime time driver can drop an internal timer entry

    crates.io

References

Freshness

Last verified in this catalog Oct 22, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • RustSec Advisory DBOct 23, 2026
  • GitHub Advisory DatabaseOct 23, 2026
  • OpenSSF OSV / OSV ScannerOct 23, 2026