Advisory record · GHSA-2f2x-8mwp-p2gc

webtransport-go: Memory Exhaustion Attack due to Missing Cleanup of Streams Map

CVSS 5.3 MediumEPSS 0.0041 · 35th percentile

Published by the GitHub Advisory Database at 12 Feb 2026, 15:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/quic-go/webtransport-goGo<0.10.00.10.0
Identifiers
GHSA-2f2x-8mwp-p2gc · CVE-2026-21438 · GO-2026-4483
Weakness (CWE)
CWE-401 · CWE-459
Published
12 Feb 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

webtransport-go versions before 0.10.0 do not remove closed streams from an internal session map, so memory grows as streams are opened and closed. A remote peer able to open WebTransport streams on a session can exhaust memory this way. Upgrade to version 0.10.0 or later, which removes closed streams from the map. No workaround is listed.

Written 1 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 (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0041, the 35th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 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.