CVE-2026-32283: 
Go vulnerability analysis and mitigation

CVE-2026-32283 is a denial-of-service vulnerability in the Go standard library's crypto/tls package affecting TLS 1.3 connections. When one side of a TLS 1.3 connection sends multiple key update messages post-handshake within a single record, the connection can deadlock, causing uncontrolled resource consumption. Affected versions include Go crypto/tls prior to 1.25.9 and versions 1.26.0 through 1.26.1. It was published on April 8, 2026, and carries a CVSS v3.1 base score of 7.5 (High) (GitHub Advisory, pkg.go.dev).

The root cause is classified as CWE-770 (Allocation of Resources Without Limits or Throttling). In TLS 1.3, the protocol permits post-handshake key update messages; however, the Go crypto/tls implementation does not properly handle the case where multiple such messages are packed into a single TLS record. This causes the connection state machine to deadlock, consuming system resources indefinitely without bound. The vulnerability is exploitable remotely with no authentication or user interaction required, as any network peer participating in a TLS 1.3 session can send a malformed record. A fix commit is available at the Go repository (go.dev CL, GitHub Advisory).

Successful exploitation results in a connection deadlock that causes uncontrolled consumption of system resources, leading to a denial-of-service condition. There is no impact on confidentiality or data integrity — the vulnerability exclusively affects availability. Any service built with a vulnerable version of Go's crypto/tls that accepts or initiates TLS 1.3 connections is at risk, including widely deployed applications such as web servers, proxies, and container orchestration components (GitHub Advisory, IBM Advisory).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time (GitHub Advisory). The EPSS score is approximately 0.007% (0.000070), indicating a very low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been reported. Despite the low exploitation evidence, the unauthenticated, network-accessible attack vector and broad ecosystem impact (Go-based applications, IBM App Connect Enterprise, rclone, Portainer, CoreDNS, and others) make patching a priority (pkg.go.dev).

1. Identify target: Locate a service built with a vulnerable version of Go's crypto/tls (Go < 1.25.9 or Go 1.26.0–1.26.1) that accepts TLS 1.3 connections, using banner grabbing or version fingerprinting tools.
2. Establish TLS 1.3 handshake: Initiate a standard TLS 1.3 connection to the target service to complete the handshake phase.
3. Craft malicious record: Construct a single TLS record containing multiple KeyUpdate messages (TLS handshake type 24) concatenated together within the same record boundary, which is not standard TLS behavior.
4. Send the malformed record: Transmit the crafted record to the target post-handshake. The vulnerable crypto/tls implementation enters a deadlock state while processing the multiple key update messages.
5. Resource exhaustion: The deadlocked connection holds system resources (goroutines, file descriptors, memory) indefinitely. Repeating this across multiple connections can exhaust server resources and cause a denial of service (go.dev CL, GitHub Advisory).

• Network: Unusual TLS 1.3 connections that remain open indefinitely without completing normal application-layer communication; high volume of persistent TLS sessions from a single source IP targeting the same service port.
• Logs: Application or server logs showing TLS connections that never close or time out; error messages related to TLS key update processing or goroutine/thread deadlocks in Go runtime logs.
• System: Abnormal growth in open file descriptors or goroutine count for Go-based services (observable via /proc/<pid>/fd or Go pprof endpoints); elevated memory consumption without corresponding application load.
• Process: Go service processes consuming CPU or memory disproportionate to traffic volume; service becoming unresponsive to new connection attempts while existing connections remain open.

Upgrade the Go standard library to version 1.25.9 (for the 1.25.x branch) or 1.26.2 (for the 1.26.x branch) or later, which contain the fix for this deadlock (pkg.go.dev, go.dev CL). Downstream consumers should rebuild and redeploy any Go-based applications using the patched Go toolchain. IBM has released a patch for IBM App Connect Enterprise Certified Container (IBM Advisory). As a temporary workaround where upgrading is not immediately possible, consider placing a TLS-terminating proxy or load balancer in front of affected services that enforces connection timeouts to limit the impact of deadlocked connections. Linux distribution vendors including Red Hat, SUSE, openSUSE, Oracle Linux, Amazon Linux, and AlmaLinux have issued updated packages (golang-announce).

The Go team disclosed the vulnerability via the golang-announce mailing list and published a fix in Go 1.25.9 and 1.26.2 (golang-announce). The vulnerability was also reported to the oss-security mailing list (oss-sec). Community discussion noted the broad downstream impact, with projects such as CoreDNS, grpc-health-probe, oauth2-proxy, Portainer, rclone, and Tailscale's Go fork all issuing updates or pull requests in response. Social media activity on Mastodon and Bluesky was modest, reflecting the low exploitation risk but broad ecosystem reach.