CVE-2026-21434 json
webtransport-go affected by Memory Exhaustion Attack due to Missing Length Check in WT_CLOSE_SESSION Capsule
published 8mo ago modified last mo. also GHSA-g6x7-jq8p-6q9q , GO-2026-4485 , EUVD-2026-6715
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
webtransport-go is an implementation of the WebTransport protocol. From 0.3.0 to 0.9.0, an attacker can cause excessive memory consumption in webtransport-go's session implementation by sending a WT_CLOSE_SESSION capsule containing an excessively large Application Error Message. The implementation does not enforce the draft-mandated limit of 1024 bytes on this field, allowing a peer to send an arbitrarily large message payload that is fully read and stored in memory. This allows an attacker to consume an arbitrary amount of memory. The attacker must transmit the full payload to achieve the memory consumption, but the lack of any upper bound makes large-scale attacks feasible given sufficient bandwidth. This vulnerability is fixed in 0.10.0.
Patch / fix
- go github.com/quic-go/webtransport-go 0.10.0
- quic-go webtransport-go 0.10.0
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260226T182644-150000.1.149.1
suse advisories SUSE-SU-2026:0757-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2026-21434 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8mo ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/quic-go/webtransport-go | >=0.3.0, <0.10.0 <0.10.0 |
0.10.0 |
| go | github.com/marten-seemann/webtransport-go | >=0.3.0 |
no fix listed |
Affected products
- quic-go webtransport-go
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/quic-go/webtransport-go/security/advisories/GHSA-g6x7-jq8p-6q9q
web, vendor-advisory, advisory
-
github.com
/quic-go/webtransport-go/releases/tag/v0.10.0
web, product, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-21434
advisory
-
github.com
/quic-go/webtransport-go
package
Sources
- CVE List CVE-2026-21434
- GitHub Advisory GHSA-g6x7-jq8p-6q9q
- NVD CVE-2026-21434
- OSV GO-2026-4485
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.