Loading vulnerability…
CVE-2026-44894 is a high-severity flaw in Netty's QUIC server implementation in io.netty:netty-codec-classes-quic. In affected versions, the default NoQuicTokenHandler used when an application does not configure its own QUIC token handler incorrectly implements token validation semantics: writeToken() does not emit a Retry token, but validateToken() unconditionally returns 0 instead of indicating failure. In QuicheQuicServerCodec.handlePacket(), any non-negative validateToken() result is interpreted as a valid token and as proof that the client's address has already been validated. As a result, a QUIC Initial packet containing any non-empty token is treated as coming from an address-validated client even when no Retry exchange occurred. This breaks the RFC 9000 Section 8.1 anti-amplification model and causes the server to proceed with quiche_accept on the validated path. The issue affects Netty 4.2.0.Final through 4.2.14.Final when the default token handler is in use and was fixed in 4.2.15.Final by changing the default validation result to -1 so tokens are treated as invalid unless explicitly validated.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Netty QUIC server vulnerability in the default NoQuicTokenHandler that incorrectly validates tokens, bypassing RFC 9000 anti-amplification protections and enabling reflection/amplification DDoS attacks.
A Netty QUIC token validation flaw that allows bypass of the anti-amplification limit and reflection of handshake traffic to a spoofed victim.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.