Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
tokio-boring versions 4.0.0 (affected range >=4.0.0, <4.1.0) contain a memory leak in how the set_ex_data function handles pre-existing data, so memory is not freed after each TLS connection completes. An attacker who can make repeated TLS connections to a program using this library can cause it to consume more resources over time, leading to denial of service through resource exhaustion. Upgrade to tokio-boring 4.1.0, which fixes the issue.
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.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA (cloudflare) |
- CISA KEV Not listed.
- EPSS 0.0062, the 50th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:18 UTC First seen by agentprime
- 31 Oct 2026, 15:18 UTC Confirmed by OSV