Race Condition Affecting topgrade package, versions <17.14.1-r2
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-TOPGRADE-21717410
- published26 Oct 2026
- disclosed23 Oct 2026
Introduced: 23 Oct 2026
NewCVE-2026-115567 (opens in a new tab)How to fix?
Upgrade Chainguard topgrade to version 17.14.1-r2 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream topgrade package and not the topgrade package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.
References
- https://github.com/tokio-rs/tokio/commit/2b4eba7833864c04ecd2f3e5f4a97ff4f6fa28d0
- https://github.com/tokio-rs/tokio/commit/5ed619bbaba87357ee5103d71b75e7c84cad99c9
- https://github.com/tokio-rs/tokio/pull/8458
- https://github.com/tokio-rs/tokio/pull/8692
- https://github.com/tokio-rs/tokio/releases/tag/tokio-1.54.1
- https://github.com/tokio-rs/tokio/security/advisories/GHSA-5wjr-9356-4wc8