CVE-2026-56862 is a resource-exhaustion denial-of-service vulnerability in Go's crypto/tls implementation. TLS handshake messages, including KeyUpdate, are treated as state-advancing irrespective of whether the TLS handshake has completed. A malicious client can repeatedly send KeyUpdate messages, causing the server to perform key-derivation operations indefinitely.
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.
146 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by Miracle Linux AXSA-2026-1830; the content provides no technical flaw details.
A denial-of-service vulnerability in Go's crypto/tls package in which indefinite TLS KeyUpdate messages can cause resource exhaustion.
A denial-of-service vulnerability in Go's crypto/tls package caused by indefinite TLS KeyUpdate messages. It affects the installed RHEL 9 delve package according to RHSA-2026:67128.
A denial-of-service vulnerability in Go's crypto/tls package caused by indefinite TLS KeyUpdate messages. It affects the installed RHEL 9 grafana-pcp package.
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.