Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain on-path network position
-
DeliveryObserve QUIC headers post-CID rotation
-
ExploitDerive reset token via HMAC
-
ExecutionCraft spoofed Stateless Reset packet
-
PersistInject packet at target endpoint
-
ImpactQUIC connection terminated
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must occupy an on-path network position between the QUIC client and server, meaning the attacker can observe QUIC packet headers as they traverse the network path - a passive wiretap, compromised router, or co-located host on the same segment would satisfy this requirement. The server must be using Netty's default HMAC-based connection-ID and stateless-reset-token generators; applications that supply custom generator implementations are not affected. A source-CID rotation must occur on the monitored connection, which is a normal QUIC protocol event but not guaranteed to happen immediately upon connection establishment. No authentication, account access, or prior relationship with the target is required by the attacker. Exploitation is specifically limited by: (1) the on-path network requirement - remote arbitrary internet hosts cannot exploit this without network-level positioning; (2) the dependency on default generator configuration; and (3) the need to observe and correctly time the CID rotation event. |
| Impact | The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L) yields a score of 4.8 Medium. The AC:H metric accurately reflects that exploitation demands an on-path network position and observation of a source-CID rotation event, making mass or opportunistic exploitation from arbitrary internet hosts unrealistic. Confidentiality impact is rated Low (C:L), capturing the information-disclosure component (token derivability), while availability impact is rated Low (A:L), reflecting the ability to terminate individual QUIC connections rather than causing persistent service outage. EPSS data was not provided in the source intelligence, so probabilistic exploitation likelihood cannot be quantified. There is no CISA KEV listing and no public proof-of-concept reported, consistent with a medium-risk rating. The chained nature of the vulnerability - information disclosure enabling targeted DoS - is operationally notable for services relying on QUIC for high-availability transport, even though neither impact is rated high in isolation. Organizations with Netty QUIC endpoints exposed on internet-accessible networks using default generator settings face the most realistic risk profile. |
| Exploit ScenarioDerived | An attacker with on-path access between a QUIC client and a Netty-based server - such as a malicious ISP node, compromised router, or co-located adversary - passively monitors QUIC packet headers during normal traffic. After a source-CID rotation event, the attacker extracts the new connection-ID bytes and applies the same HMAC derivation used by Netty's default generator to compute the stateless reset token. The attacker then crafts a spoofed Stateless Reset packet containing the derived token and injects it toward the server or client, causing the targeted endpoint to interpret it as a legitimate reset and abruptly terminate the QUIC connection. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 12, 2026
Stateless reset token leakage in Netty's QUIC codec (io.netty:netty-codec-classes-quic prior to 4.2.15.Final) enables an on-path attacker to derive the reset token for active connections and terminate them via spoofed Stateless Reset packets. The default HMAC-based generators expose a deterministic relationship between the source connection ID visible in QUIC headers and the server's stateless reset token - after a source-CID rotation, an observer can compute the token from the new connection-ID bytes. No public exploit identified at time of analysis; the CVSS 4.8 Medium rating reflects the on-path attacker prerequisite (AC:H), which meaningfully limits opportunistic exploitation.
RemediationAI
Upgrade to Netty 4.2.15.Final, which patches this vulnerability along with multiple other security fixes in the same release batch. The patched release is available at https://github.com/netty/netty/releases/tag/netty-4.2.15.Final and via Maven Central as io.netty:netty-codec-classes-quic:4.2.15.Final. The security advisory is at https://github.com/netty/netty/security/advisories/GHSA-cq4q-cv5g-r8q5. If immediate upgrade is not possible, a targeted workaround is to replace the default HMAC-based connection-ID and stateless-reset-token generators with a custom implementation that does not derive the reset token from connection-ID bytes, removing the exploitable relationship; this requires Netty API familiarity and carries a regression risk if the replacement is not cryptographically sound. As a network-layer compensating control, restricting on-path access to QUIC traffic (e.g., encrypted tunnels, network segmentation, or limiting QUIC to trusted network segments) reduces attacker positioning opportunities but does not eliminate the underlying flaw and may not be feasible for internet-facing deployments.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
QUIC (RFC 9000) supports stateless reset packets, allowing endpoints to abort connections without per-connection state. Each connection ID has an associated stateless reset token; possession of this token allows any party to terminate the corresponding connection. Netty's default HMAC-based connection-ID and stateless-reset-token generator introduces a deterministic mathematical relationship between the connection ID - visible in QUIC packet headers on the network path - and the reset token. After a source-CID rotation, a normal QUIC protocol event, the new connection-ID bytes carry sufficient information for an on-path observer to reconstruct the reset token via the same HMAC operation. This is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) because a value that should remain private (the reset token) becomes derivable from public header fields. The affected artifact is io.netty:netty-codec-classes-quic, covered by CPE cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:* for all Netty releases prior to 4.2.15.Final.
Know when Netty gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L
On-path position and CID rotation observation required (AC:H); no attacker authentication needed; token derivability warrants C:L; connection termination warrants A:L only.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Netty is a network application framework for development of protocol servers and clients. Prior to version 4.2.15.Final, Netty QUIC exposes the stateless reset token on the network path when using the default HMAC-based connection-ID and stateless-reset-token generators. The reset token for the server's current source connection ID can be derived from bytes that appear as the connection ID in QUIC headers after a source-CID rotation. An on-path attacker observing the headers can use the token to perform a Denial of Service by sending a spoofed Stateless Reset packet. Version 4.2.15.Final patches the issue.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Netty before 4.1.42.Final mishandles whitespace before the colon in HTTP headers (such as a "Transfer-Encoding : chunked
Certificate revocation-check bypass in the Netty network framework's OCSP client (io.netty:netty-handler-ssl-ocsp) affec
netty-incubator-codec-ohttp is the OHTTP implementation for netty. Rated critical severity (CVSS 9.1), this vulnerabilit
The netty incubator codec.bhttp is a java language binary http parser. Rated high severity (CVSS 8.1), this vulnerabilit
Netty, an asynchronous, event-driven network application framework, has a vulnerability starting in version 4.1.91.Final
Memory exhaustion in Netty's SctpMessageCompletionHandler (netty-transport-sctp) allows unauthenticated remote peers to
Compression-amplification denial of service in the Netty network framework (versions prior to 4.1.136.Final and 4.2.16.F
Memory-amplification denial of service in the Netty network framework (SPDY/3.1 codec) prior to 4.1.136.Final and 4.2.16
Memory-exhaustion denial of service in Netty's HTTP/3 codec (Http3FrameCodec) affects all releases prior to 4.2.16.Final
Netty's HTTP CORS handler silently rewrites the Vary response header to Vary: Origin in releases before 4.1.137.Final an
Denial of service in the Netty HTTP/3 codec (io.netty:netty-codec-http3) prior to version 4.2.15.Final allows remote una
EUVD-2026-36462
GHSA-cq4q-cv5g-r8q5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB