TI-2026-32769 Aliases CVE-2026-44894 GHSA-cmm3-54f8-px4j

Netty's Default QUIC token handler accepts any client-supplied token

LOW 38CWE-940Published 2026-06-12 · Updated 2026-07-15

Key facts

Attack vector: Network
Privileges required: None
User interaction: None
Attack complexity: Low
Impact type: —
Confidentiality · integrity · availability: None · High · None
Fix status: Partial Red Hat: 1 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA, GitHub and Red Hat.

Summary

Netty is a network application framework for development of protocol servers and clients. NoQuicTokenHandler is the tokenHandler used when the application does not set one. Prior to version 4.2.15.Final, its writeToken() returns false (server will not send Retry — acceptable), but validateToken() unconditionally `return 0`. In QuicheQuicServerCodec.handlePacket(), a non-negative return from validateToken() is interpreted as 'token is valid, ODCID starts at offset 0', causing the server to call quiche_accept as if the client's address had been validated by a Retry round-trip. Per RFC 9000 §8.1, a validated address lifts the 3× anti-amplification send limit. Thus any attacker who includes ANY non-empty token bytes in an Initial packet — with a spoofed victim source IP — causes the Netty server to treat the victim as validated and reflect full-size handshake flights (certificates, etc.) toward it without the 3× cap. The correct 'no token handler' semantics would be to return -1 (invalid) so the normal un-validated path and amplification limit apply. Version 4.2.15.Final patches the issue.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV

EPSS 0.00143 3rd percentileScored 2026-11-07

Fix Partial netty (netty): 4.2.15.Finalio.netty:netty-codec-classes-quic (Maven): 4.2.15.FinalRed Hat: 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation: None
Automatable: Yes
Technical impact: Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

Vendor	Product	Affected versions	Fixed in	Status	Source
netty	netty	4.2.0.Final to before 4.2.15.Final	4.2.15.Final	Patch available	CNA
—	io.netty:netty-codec-classes-quic (Maven)	4.2.0.Final to before 4.2.15.Final	4.2.15.Final	Patch available	GHSA-cmm3-54f8-px4j

netty Vendornetty Affected 4.2.0.Final to before 4.2.15.Final Fixed in 4.2.15.Final Patch available CNA
io.netty:netty-codec-classes-quic (Maven) Vendor— Affected 4.2.0.Final to before 4.2.15.Final Fixed in 4.2.15.Final Patch available GHSA-cmm3-54f8-px4j

CPE configurations NVD · 1

CPE	Versions	Role	Vendor
cpe:2.3:a:netty:netty::::::::	4.2.0 to before 4.2.15	Vulnerable	netty

cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:* Versions 4.2.0 to before 4.2.15 Vulnerable ·netty

Remediation

Fix · CNA netty (netty) Fixed in 4.2.15.Final
Fix · GHSA-cmm3-54f8-px4j io.netty:netty-codec-classes-quic (Maven) Fixed in 4.2.15.Final Advisory →

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

Product	Status	Plan or fix
Red Hat build of Apache Camel - HawtIO 4	Affected	No fix yet

Timeline

2026-10-02 Threatist record created from CVE-2026-44894
2026-10-03 Alias added: GHSA-cmm3-54f8-px4j

References

Advisory 2

Other 2

TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
TI-2026-30861 Netty: HTTP/1.0 TE+CL Coexistence Bypasses Smuggling Sanitization CVSS 3.1CRITICAL 9.8
TI-2026-30864 Netty: HttpClientCodec response desynchronization CVSS 3.1CRITICAL 9.1
TI-2026-30859 Netty: DNS Codec Input Validation Bypass in Netty (Encoder + Decoder) CVSS 3.1CRITICAL 9.1
TI-2026-40973 Netty: Missing CertificateID Validation in OCSP Response Allows Replay Attacks CVSS 3.1CRITICAL 9.1
TI-2026-40972 Uncontrolled resource consumption in netty CVSS 3.1HIGH 7.5

See all 92 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences