CVE-2025-29908 json
Netty QUIC hash collision DoS attack
published 2025-03-31 19 mo ago modified 2026-06-17 4 mo ago also GHSA-hqqc-jr88-p6x2 , EUVD-2025-9052
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
Netty QUIC codec is a QUIC codec for netty which makes use of quiche. An issue was discovered in the codec. A hash collision vulnerability (in the hash map used to manage connections) allows remote attackers to cause a considerable CPU load on the server (a Hash DoS attack) by initiating connections with colliding Source Connection IDs (SCIDs). This vulnerability is fixed in 0.0.71.Final.
Patch / fix
- maven io.netty.incubator:netty-incubator-codec-quic 0.0.71.Final
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 |
| 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 |
|---|---|---|---|
| maven | io.netty.incubator:netty-incubator-codec-quic | <0.0.71.Final |
0.0.71.Final |
Affected products
- netty netty-incubator-codec-quic
Classification
- Weakness
-
- CWE-407 Inefficient Algorithmic Complexity
References
-
github.com
/netty/netty-incubator-codec-quic/commit/e059bd9b78723f8b035e0c547e42ce263f03461c
web
-
github.com
/netty/netty-incubator-codec-quic/security/advisories/GHSA-hqqc-jr88-p6x2
web
-
github.com
/ncc-pbottine/QUIC-Hash-Dos-Advisory
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-29908
advisory
-
github.com
/netty/netty-incubator-codec-quic
package
Sources
- CVE List CVE-2025-29908
- GitHub Advisory GHSA-hqqc-jr88-p6x2
- NVD CVE-2025-29908
Fencer Vulns 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.