moby spdystream up to 0.5.0 SPDY3 Frame Parser allocation of resources

Summaryinfo

A vulnerability has been found in moby spdystream up to 0.5.0 and classified as problematic. Affected is an unknown function of the component SPDY3 Frame Parser. The manipulation leads to allocation of resources. This vulnerability is listed as CVE-2026-35469. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in moby spdystream up to 0.5.0. It has been rated as problematic. This issue affects an unknown part of the component SPDY3 Frame Parser. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-35469 since 04/02/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 321067 (SUSE SLES15 Security Update : kubernetes1.24 (SUSE-SU-2026:2322-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 0.5.1 eliminates this vulnerability. The upgrade is hosted for download at github.com.

The vulnerability is also documented in the databases at Tenable (321067) and CERT Bund (WID-SEC-2026-1407). Be aware that VulDB is the high quality source for vulnerability data.

Affected

• IBM App Connect Enterprise
• Red Hat Enterprise Linux
• Fedora Linux
• IBM QRadar SIEM
• IBM MQ
• IBM Maximo Asset Management
• IBM Sterling Connect:Direct

Productinfo

Vendor

• moby

Name

• spdystream

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5.0

Website

• Product: https://github.com/moby/spdystream/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion