CVE-2026-35469: CWE-770: Allocation of Resources Without Limits or Throttling in moby spdystream
CVE-2026-35469 is a high-severity vulnerability in the spdystream Go library (versions 0. 5. 0 and below) used for multiplexing streams over SPDY connections. The SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory, leading to unbounded allocations. This affects SETTINGS frame entry counts, header counts, and individual header field sizes, all used directly as allocation sizes without bounds checking. Due to SPDY header blocks being zlib-compressed, a small payload can decompress into large values, allowing a remote attacker to exhaust process memory and cause an out-of-memory crash with a crafted control frame. The issue is fixed in version 0. 5. 1.
AI Analysis
Technical Summary
The spdystream library versions prior to 0.5.1 contain a resource exhaustion vulnerability (CWE-770) due to lack of validation on attacker-controlled counts and lengths in SPDY/3 frame parsing. Specifically, the SETTINGS frame entry count, header count in parseHeaderValueBlock, and individual header field sizes are read as 32-bit integers and used directly for memory allocation without bounds checking. Because SPDY header blocks are compressed with zlib, a small compressed payload can expand into large memory allocations. A remote peer sending crafted SPDY frames can exploit this to exhaust memory and crash the process. This vulnerability has been addressed in spdystream version 0.5.1.
Potential Impact
An unauthenticated remote attacker able to send SPDY frames to a service using vulnerable spdystream versions can cause the service to exhaust its memory and crash, resulting in a denial of service. There is no indication of code execution or data disclosure. The impact is high due to the ease of triggering an out-of-memory condition remotely.
Mitigation Recommendations
Upgrade spdystream to version 0.5.1 or later, where this vulnerability is fixed. Since the vendor advisory or patch links are not explicitly provided, confirm the update from the official spdystream or moby project sources. Patch status is not yet confirmed from vendor advisory content in this data; check vendor sources for current remediation guidance.
CVE-2026-35469: CWE-770: Allocation of Resources Without Limits or Throttling in moby spdystream
Description
CVE-2026-35469 is a high-severity vulnerability in the spdystream Go library (versions 0. 5. 0 and below) used for multiplexing streams over SPDY connections. The SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory, leading to unbounded allocations. This affects SETTINGS frame entry counts, header counts, and individual header field sizes, all used directly as allocation sizes without bounds checking. Due to SPDY header blocks being zlib-compressed, a small payload can decompress into large values, allowing a remote attacker to exhaust process memory and cause an out-of-memory crash with a crafted control frame. The issue is fixed in version 0. 5. 1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The spdystream library versions prior to 0.5.1 contain a resource exhaustion vulnerability (CWE-770) due to lack of validation on attacker-controlled counts and lengths in SPDY/3 frame parsing. Specifically, the SETTINGS frame entry count, header count in parseHeaderValueBlock, and individual header field sizes are read as 32-bit integers and used directly for memory allocation without bounds checking. Because SPDY header blocks are compressed with zlib, a small compressed payload can expand into large memory allocations. A remote peer sending crafted SPDY frames can exploit this to exhaust memory and crash the process. This vulnerability has been addressed in spdystream version 0.5.1.
Potential Impact
An unauthenticated remote attacker able to send SPDY frames to a service using vulnerable spdystream versions can cause the service to exhaust its memory and crash, resulting in a denial of service. There is no indication of code execution or data disclosure. The impact is high due to the ease of triggering an out-of-memory condition remotely.
Mitigation Recommendations
Upgrade spdystream to version 0.5.1 or later, where this vulnerability is fixed. Since the vendor advisory or patch links are not explicitly provided, confirm the update from the official spdystream or moby project sources. Patch status is not yet confirmed from vendor advisory content in this data; check vendor sources for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-02T20:49:44.452Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e1554682d89c981fce0d7f
Added to database: 4/16/2026, 9:31:50 PM
Last enriched: 4/16/2026, 9:46:57 PM
Last updated: 4/16/2026, 10:37:50 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.