CVE-2026-35469
spdystream is a Go library for multiplexing streams over SPDY …
spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/moby/spdystream/releases/tag/v0.5.1
- github.com/moby/spdystream/security/advisories/GHSA-pc3f-x583-g7j2
- github.com/advisories/GHSA-pc3f-x583-g7j2
- nvd.nist.gov/vuln/detail/CVE-2026-35469
- github.com/moby/spdystream/commit/ef6121f62c730110bf5ae604a865a8613bfb787f
- access.redhat.com/errata/RHSA-2026:11070
- access.redhat.com/errata/RHSA-2026:11217
- access.redhat.com/errata/RHSA-2026:12118
- nvd.nist.gov/vuln/detail/CVE-2026-35469
- cve.org/CVERecord?id=CVE-2026-35469
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.