CVE-2026-32283 is a denial-of-service vulnerability in the Go standard library's crypto/tls implementation. When a TLS peer sends multiple post-handshake KeyUpdate messages within a single TLS record, the connection can deadlock, causing uncontrolled resource consumption. The vulnerability affects only TLS 1.3.
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.
203 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A TLS 1.3 denial-of-service vulnerability in the stdlib library. Multiple post-handshake key update messages in a single record can deadlock a connection and cause uncontrolled resource consumption. The reference assigns a CVSS v3 base score of 7.5 and recommends upgrading stdlib and related packages to version 1.25.9 or later.
A network-accessible denial-of-service vulnerability in Go crypto/tls that can be triggered using multiple TLS 1.3 KeyUpdate messages.
Unknown
A vulnerability covered by an AlmaLinux 9.6 local security update/check. The content does not provide technical vulnerability details.
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.