Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/moby/spdystream/releases/tag/v0.5.1
- https://github.com/moby/spdystream/security/advisories/GHSA-pc3f-x583-g7j2
FAQ
What is CVE-2026-35469?
CVE-2026-35469 is a documented vulnerability. 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 allocati...
How severe is CVE-2026-35469?
CVSS scoring is not yet available for CVE-2026-35469. Check NVD for updates.
Is there a patch for CVE-2026-35469?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.