CVE-2026-35469
Description
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.
How to fix
- github.com/moby/spdystream0.5.1 or later
- access.redhat.com/errata/RHSA-2026:41019
- access.redhat.com/errata/RHSA-2026:36796
- access.redhat.com/errata/RHSA-2026:51422
- access.redhat.com/errata/RHSA-2026:34755
- access.redhat.com/errata/RHSA-2026:61314
- access.redhat.com/errata/RHSA-2026:66521
- access.redhat.com/errata/RHSA-2026:17704
- access.redhat.com/errata/RHSA-2026:11070
- access.redhat.com/errata/RHSA-2026:11217
- access.redhat.com/errata/RHSA-2026:13791
- access.redhat.com/errata/RHSA-2026:13829
- access.redhat.com/errata/RHSA-2026:53655
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| github.com/moby/spdystreamGo | v < 0.5.1 | 0.5.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.