CVE-2026-45416 is an uncontrolled memory-consumption vulnerability in Netty's netty-handler module. Before 4.1.135.Final and 4.2.15.Final, SslClientHelloHandler.decode() parses an attacker-controlled 24-bit TLS handshake length and, if a ClientHello spans TLS records, immediately allocates a buffer of that declared size. The default SniHandler and AbstractSniHandler construction paths set maxClientHelloLength to zero, disabling the length check, and also set no handshake timeout. An attacker can therefore induce an immediate allocation of up to approximately 16 MiB per TLS connection; allocations beyond the pooled chunk size may be unpooled. The allocated buffer is retained until the channel closes.
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.
41 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Netty handler denial-of-service flaw caused by eager buffer allocation during TLS handshake processing.
A denial-of-service vulnerability in Netty's handler component caused by eager buffer allocation during the TLS handshake.
A Netty handler vulnerability that can cause denial of service due to eager buffer allocation during the TLS handshake.
A Netty denial-of-service vulnerability caused by eager buffer allocation during the TLS handshake.
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.