NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-57497: webtransport-go: Memory Exhaustion Attack due to Buffering of Unknown Capsules

mediumCVSS 3.1 5.3GHSA-g35j-m5xg-vh3q

Summary An attacker can cause excessive memory allocation in webtransport-go by sending an unknown WebTransport capsule with a large payload. The implementation skips unknown capsules by reading the entire capsule body into memory, instead of draining it without retaining the data. This can lead to memory exhaustion.

Published Jul 24, 2026

Affected packages

github.com/quic-go/webtransport-go

Ecosystem
Go
Affected
<= 0.11.0
Fixed in
0.11.1
Check
go list -m github.com/quic-go/webtransport-go

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

An attacker can cause excessive memory allocation in webtransport-go by sending an unknown WebTransport capsule with a large payload. The implementation skips unknown capsules by reading the entire capsule body into memory, instead of draining it without retaining the data. This can lead to memory exhaustion.

Impact

A misbehaving or malicious peer can cause a denial-of-service (DoS) attack against webtransport-go clients or servers by triggering excessive memory allocation, potentially leading to crashes or resource exhaustion.

Details

WebTransport sessions use capsules on the HTTP/3 request stream. Unknown capsule types are ignored, but the capsule body still needs to be consumed before the next capsule can be parsed.

webtransport-go used io.ReadAll when skipping unknown capsules. Since the capsule reader is only limited by the capsule's declared length, a peer could send a large unknown capsule and cause the receiver to allocate memory for the full capsule body.

QUIC flow control limits buffered data, but it does not bound total allocation here, since reading the stream advances the flow control window while retaining the received bytes in memory.

The Fix

webtransport-go now drains unknown capsules to io.Discard instead of buffering them. This consumes the capsule body so parsing can continue, without retaining the payload in memory.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries