Vulnerability record · CVE-2026-56855 · published 2 September 2026
CVE-2026-56855: Golang crypto allocation without limits vulnerability
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.
Description
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://go.dev/cl/826524 | Patch |
| https://go.dev/issue/81317 | Issue TrackingVendor Advisory |
| https://groups.google.com/g/golang-announce/c/1y3fb2np35U | Mailing ListVendor Advisory |
| https://pkg.go.dev/vuln/GO-2026-6355 | Vendor Advisory |
Track CVE-2026-56855 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2026-56855), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.