Answer in brief
CVE-2026-56862 records a Unknown severity vulnerability in Limit handshake messages we are willing to accept post-handshake in crypto/tls. The current sources do not mark it as known exploited. The current feed maps Go standard library/crypto/tls (generic), stdlib (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Go standard library/crypto/tls (generic), stdlib (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Go standard library/crypto/tlsgeneric | >=0 <1.25.13 || >=1.26.0-0 <1.26.6 || >=1.27.0-0 <1.27.0-rc.3 | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| stdlibgo | >=0 <1.25.13 >=1.26.0-0 <1.26.6 >=1.27.0-0 <1.27.0-rc.3 | 1.25.13, 1.26.6, 1.27.0-rc.3 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 13, 2026
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-56862 records a Unknown severity vulnerability in Limit handshake messages we are willing to accept post-handshake in crypto/tls. The current sources do not mark it as known exploited. The current feed maps Go standard library/crypto/tls (generic), stdlib (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Go standard library/crypto/tls (generic), stdlib (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Go standard library/crypto/tlsgeneric | >=0 <1.25.13 || >=1.26.0-0 <1.26.6 || >=1.27.0-0 <1.27.0-rc.3 | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| stdlibgo | >=0 <1.25.13 >=1.26.0-0 <1.26.6 >=1.27.0-0 <1.27.0-rc.3 | 1.25.13, 1.26.6, 1.27.0-rc.3 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 13, 2026
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.
Quoted source text, attributed separately from HOL analysis.