Advisory record · GHSA-pjrj-h4fg-6gm4

tokio-boring vulnerable to resource exhaustion via memory leak

CVSS 5.3 MediumEPSS 0.0062 · 50th percentile

Published by the GitHub Advisory Database at 5 Dec 2023, 23:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
tokio-boringcrates.io>=4.0.0, <4.1.04.1.0
Identifiers
GHSA-pjrj-h4fg-6gm4 · CVE-2023-6180
Weakness (CWE)
CWE-400 · CWE-401 · CWE-404
Published
5 Dec 2023
Updated
8 Jul 2026

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.

Written 8 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 15:18 UTC First seen by agentprime
  2. 31 Oct 2026, 15:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.