CVE-2026-56855
highPreviously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection.
Vendor / product: Golang — crypto
Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and tear the connection down instead of buffering and blocking.
CVSS
7.5
7.5 (CVSS v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Severity source: NVD CVSS v3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
Timeline (UTC)
Published: 2026-09-02 20:17
Modified: 2026-09-04 16:34
NVD status: Analyzed
Last synced 1 day ago
Verified against the source API 2026-10-27 06:50 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
golang / crypto <0.56.0
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
Vendor advisory: https://go.dev/issue/81317
Vendor advisory: https://groups.google.com/g/golang-announce/c/1y3fb2np35U
Vendor advisory: https://pkg.go.dev/vuln/GO-2026-6355
Patch / mitigation: https://go.dev/cl/826524
References
- https://go.dev/cl/826524 security@golang.org
- https://go.dev/issue/81317 security@golang.org
- https://groups.google.com/g/golang-announce/c/1y3fb2np35U security@golang.org
- https://pkg.go.dev/vuln/GO-2026-6355 security@golang.org
Data sources
NVD CVE API 2.0 — fetched 2026-10-27 06:50 UTC · record ↗