Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Tokio versions 1.54.0 (affected range >=1.54.0, <1.54.1) have a race condition in tokio::time::Interval on the multi-threaded runtime, where Interval::poll_tick or .tick().await can drop a timer entry without synchronizing with the time driver. The source says this can cause data races and use-after-free conditions, leading to crashes, panics, or memory corruption, with no attacker action described beyond normal use of Interval. Upgrade to tokio 1.54.1, which contains the fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.8 | Medium | 4.0 | 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 | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0011, the 1st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV