Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.

Go's spdystream Library Fails to Validate Memory Allocation

DEBIAN-CVE-2026-35469
Summary

A vulnerability in the spdystream library for Go can cause a service to consume all available memory and crash. This can happen if a malicious peer sends a specially crafted message to the service. The issue has been fixed in version 0.5.1, so upgrading to this version is recommended.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software
Ecosystem VendorProductAffected versions
Debian:11 debian golang-github-docker-spdystream All versions
Debian:12 debian golang-github-docker-spdystream All versions
Debian:13 debian golang-github-docker-spdystream All versions
Debian:14 debian golang-github-docker-spdystream All versions
Original title
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 alloc...
Original 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.
Published: 16 Apr 2026 · Updated: 17 Apr 2026 · First seen: 17 Apr 2026