Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.8amended

Tokio: Race condition in tokio::time::Interval

CVE-2026-115567GHSA-5wjr-9356-4wc8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tokio 1.54.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io tokio

    Affected
    >= 1.54.0, <= 1.54.0
    Fixed in
    1.54.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.8 · 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 · score source
EPSS
  • CVE-2026-115567: 0.11% estimated exploitation activity in the next 30 days; percentile 1.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary On the multi-threaded runtime, there is a race condition between Interval::polltick and the runtime's time driver. This affects Interval only. Sleep and Timeout are not affected. Details In Tokio v1.54.0, a race condition between tokio::time::Interval::polltick (including .tick().await) 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 Interval 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 5 · amended ·

    Amended from ghsa record GHSA-5wjr-9356-4wc8

  2. Revision 4 · amended ·

    Amended from ghsa record GHSA-5wjr-9356-4wc8

  3. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  4. Revision 2 · amended ·

    Amended from osv record RUSTSEC-2026-0384

  5. Revision 1 · created ·

    Published from osv record GHSA-5wjr-9356-4wc8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-115567

Advisory: Tokio: Race condition in `tokio::time::Interval`
IDs: CVE-2026-115567, GHSA-5wjr-9356-4wc8
Record: https://patchnext.com/advisories/cve-2026-115567 (revision 5, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tokio 1.54.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io tokio: affected >= 1.54.0, <= 1.54.0; fixed in 1.54.1

## Suggested inspection (read-only)
- crates.io tokio: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tokio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5wjr-9356-4wc8 (OSV record GHSA-5wjr-9356-4wc8 lists affected ranges: crates.io tokio >=1.54.0 <1.54.1 (fixed))
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0384 (OSV record RUSTSEC-2026-0384 lists affected ranges: crates.io tokio >=1.54.0 <1.54.1 (fixed))
- Verified: https://github.com/advisories/GHSA-5wjr-9356-4wc8 (GitHub-reviewed advisory GHSA-5wjr-9356-4wc8 lists affected ranges: crates.io tokio >=1.54.0 <=1.54.0)

Commands are suggestions: review each one before running it.

Loading voting…