CVE-2026-32283: CWE-667: Improper Locking in Go standard library crypto/tls
If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.
AI Analysis
Technical Summary
This vulnerability arises from improper locking (CWE-667) in the Go standard library's crypto/tls implementation of TLS 1.3. Specifically, when multiple key update messages are sent post-handshake in a single record, the connection can enter a deadlock state. This deadlock leads to uncontrolled consumption of system resources, causing a denial of service condition. The flaw affects Go versions from 0 up to 1.26.0-0. No CVSS score or official remediation level is currently available.
Potential Impact
The vulnerability can cause a denial of service by deadlocking TLS 1.3 connections in affected Go applications. This results in uncontrolled resource consumption, potentially degrading service availability. There is no evidence of exploitation in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should monitor updates from the Go project. No vendor advisory or patch links are currently available.
CVE-2026-32283: CWE-667: Improper Locking in Go standard library crypto/tls
Description
If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from improper locking (CWE-667) in the Go standard library's crypto/tls implementation of TLS 1.3. Specifically, when multiple key update messages are sent post-handshake in a single record, the connection can enter a deadlock state. This deadlock leads to uncontrolled consumption of system resources, causing a denial of service condition. The flaw affects Go versions from 0 up to 1.26.0-0. No CVSS score or official remediation level is currently available.
Potential Impact
The vulnerability can cause a denial of service by deadlocking TLS 1.3 connections in affected Go applications. This results in uncontrolled resource consumption, potentially degrading service availability. There is no evidence of exploitation in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should monitor updates from the Go project. No vendor advisory or patch links are currently available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Go
- Date Reserved
- 2026-03-11T16:38:46.556Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d5da2d43e2781badfbe690
Added to database: 4/8/2026, 4:31:41 AM
Last enriched: 4/8/2026, 4:47:00 AM
Last updated: 4/8/2026, 7:41:37 AM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.