CVE-2026-32283 is a denial-of-service vulnerability in the Go standard library's crypto/tls package affecting TLS 1.3 connections. The flaw is triggered when a peer sends multiple post-handshake TLS 1.3 KeyUpdate messages within a single TLS record. Under this condition, the affected implementation can enter a connection deadlock state, resulting in uncontrolled resource consumption. The issue is remotely reachable over the network and does not require authentication or user interaction. The weakness has been associated with improper handling of repeated locking or state transitions and is mapped to CWE-764.
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.
150 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service vulnerability in Go crypto/tls triggered by multiple TLS 1.3 key update messages.
A denial-of-service vulnerability in Go's crypto/tls implementation triggered by multiple TLS 1.3 key update messages.
A Go crypto/tls denial-of-service vulnerability triggered by multiple TLS 1.3 key update messages.
A Go crypto/tls denial of service vulnerability via multiple TLS 1.3 key update messages.
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.