Medium · CVSS 5.8CVE-2026-115567

Tokio: Race condition in `tokio::time::Interval`CVE-2026-115567

Answer in brief

CVE-2026-115567 records a Medium severity (CVSS 5.8) vulnerability in Tokio: Race condition in `tokio::time::Interval`. The current sources do not mark it as known exploited. The current feed maps tokio-rs/tokio (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 23, 2026Updated Oct 23, 2026Source checked Oct 23, 2026First seen by HOL Oct 23, 2026Material review Oct 23, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.8
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 5.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps tokio-rs/tokio (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
tokio-rs/tokiogeneric	= 1.54.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for tokio-rs/tokio.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 23, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.