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 moby spdystream Go library versions 0. 5. 0 and below. The SPDY/3 frame parser fails to validate attacker-controlled counts and lengths before allocating memory, leading to unbounded allocations. This affects three allocation paths: SETTINGS frame entry count, header count in parseHeaderValueBlock, and individual header field sizes. Because SPDY header blocks are 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 single crafted frame. The issue is fixed in version 0. 5. 1.
AI Analysis
Technical Summary
The spdystream library for multiplexing SPDY streams in Go versions prior to 0.5.1 contains a resource exhaustion vulnerability (CWE-770). The SPDY/3 frame parser does not perform bounds checking on attacker-controlled 32-bit integer values used for memory allocation in three key areas: SETTINGS frame entry count, header count, and individual header field sizes. Due to zlib compression of SPDY header blocks, a small compressed payload can expand to large memory allocations, enabling a remote attacker to cause an out-of-memory crash by sending a crafted SPDY control frame. This vulnerability has a CVSS 4.0 score of 8.7 (high severity) and was fixed in spdystream version 0.5.1.
Potential Impact
A remote unauthenticated attacker can send a specially crafted SPDY frame to a service using a vulnerable spdystream version, causing excessive memory allocation and leading to an out-of-memory crash. This results in denial of service due to process termination or instability. There is no indication of code execution or data disclosure from the provided data.
Mitigation Recommendations
Upgrade spdystream to version 0.5.1 or later, where this vulnerability is fixed. Since no official patch link or vendor advisory is provided, confirm the upgrade from the official moby/spdystream repository or release notes. Patch status is not yet confirmed from a vendor advisory, so check the vendor's official channels 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 moby spdystream Go library versions 0. 5. 0 and below. The SPDY/3 frame parser fails to validate attacker-controlled counts and lengths before allocating memory, leading to unbounded allocations. This affects three allocation paths: SETTINGS frame entry count, header count in parseHeaderValueBlock, and individual header field sizes. Because SPDY header blocks are 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 single crafted frame. The issue is fixed in version 0. 5. 1.
CVSS v4.0
Score 8.7high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The spdystream library for multiplexing SPDY streams in Go versions prior to 0.5.1 contains a resource exhaustion vulnerability (CWE-770). The SPDY/3 frame parser does not perform bounds checking on attacker-controlled 32-bit integer values used for memory allocation in three key areas: SETTINGS frame entry count, header count, and individual header field sizes. Due to zlib compression of SPDY header blocks, a small compressed payload can expand to large memory allocations, enabling a remote attacker to cause an out-of-memory crash by sending a crafted SPDY control frame. This vulnerability has a CVSS 4.0 score of 8.7 (high severity) and was fixed in spdystream version 0.5.1.
Potential Impact
A remote unauthenticated attacker can send a specially crafted SPDY frame to a service using a vulnerable spdystream version, causing excessive memory allocation and leading to an out-of-memory crash. This results in denial of service due to process termination or instability. There is no indication of code execution or data disclosure from the provided data.
Mitigation Recommendations
Upgrade spdystream to version 0.5.1 or later, where this vulnerability is fixed. Since no official patch link or vendor advisory is provided, confirm the upgrade from the official moby/spdystream repository or release notes. Patch status is not yet confirmed from a vendor advisory, so check the vendor's official channels 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/24/2026, 4:20:30 PM
Last updated: 6/2/2026, 5:45:08 AM
Views: 121
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.