CVE-2026-35469: SpdyStream Denial of Service Vulnerability
HIGHCVE-2026-35469 is a HIGH denial of service vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting SpdyStream libraries in the Go ecosystem. The issue involves dos on cri. Remediation is available by upgrading affected packages to version 0.5.1.
CVE-2026-35469 at a Glance
How to Fix CVE-2026-35469
To remediate this vulnerability, upgrade all affected SpdyStream dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/moby/spdystream to 0.5.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/moby/spdystream
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-35469, inspect your project dependencies for SpdyStream:
inspect dependencies for github.com/moby/spdystream
Analyze the terminal output to locate any version of SpdyStream in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.5.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In SpdyStream, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-35469 Affected SpdyStream Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/moby/spdystream
|
Go |
< 0.5.1
|
0.5.1
|
References
Frequently Asked Questions
What is CVE-2026-35469?
Which SpdyStream versions are affected?
What version fixes CVE-2026-35469?
Is github.com/moby/spdystream affected?
What CWE is associated with CVE-2026-35469?
How can I check Go dependencies for CVE-2026-35469?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pc3f-x583-g7j2",
"modified" : "2026-06-08T23:36:28Z",
"published" : "2026-04-16T20:44:01Z",
"aliases" : [ "CVE-2026-35469" ],
"summary" : "SpdyStream: DOS on CRI",
"details" : "The SPDY/3 frame parser in spdystream does not validate\nattacker-controlled counts and lengths before allocating memory. A\nremote peer that can send SPDY frames to a service using spdystream can\ncause the process to allocate gigabytes of memory with a small number of\nmalformed control frames, leading to an out-of-memory crash.\n \nThree allocation paths in the receive side are affected:\n1. **SETTINGS entry count** -- The SETTINGS frame reader reads a 32-bit\n`numSettings` from the payload and allocates a slice of that size\nwithout checking it against the declared frame length. An attacker\ncan set `numSettings` to a value far exceeding the actual payload,\ntriggering a large allocation before any setting data is read.\n \n2. **Header count** -- `parseHeaderValueBlock` reads a 32-bit\n`numHeaders` from the decompressed header block and allocates an\n`http.Header` map of that size with no upper bound.\n \n3. **Header field size** -- Individual header name and value lengths are\nread as 32-bit integers and used directly as allocation sizes with\nno validation.\n \nBecause SPDY header blocks are zlib-compressed, a small on-the-wire\npayload can decompress into attacker-controlled bytes that the parser\ninterprets as 32-bit counts and lengths. A single crafted frame is\nenough to exhaust process memory.\n## Impact\n Any program that accepts SPDY connections using spdystream -- directly\nor through a dependent library -- is affected. A remote peer that can\nsend SPDY frames to the service can crash the process with a single\ncrafted SPDY control frame, causing denial of service.\n## Affected versions\n `github.com/moby/spdystream` <= v0.5.0\n## Fix\n v0.5.1 addresses the receive-side allocation bugs and adds related\nhardening:\n \n**Core fixes:**\n \n- **SETTINGS entry-count validation** -- The SETTINGS frame reader now\nchecks that `numSettings` is consistent with the declared frame\nlength (`numSettings <= (length-4)/8`) before allocating.\n \n- **Header count limit** -- `parseHeaderValueBlock` enforces a maximum\nnumber of headers per frame (default: 1000).\n \n- **Header field size limit** -- Individual header name and value\nlengths are checked against a per-field size limit (default: 1 MiB)\nbefore allocation.\n \n- **Connection closure on protocol error** -- The connection read loop\nnow closes the underlying `net.Conn` when it encounters an\n`InvalidControlFrame` error, preventing further exploitation on the\nsame connection.\n \n**Additional hardening:**\n \n- **Write-side bounds checks** -- All frame write methods now verify\nthat payloads fit within the 24-bit length field, preventing the\nlibrary from producing invalid frames.\n \n**Configurable limits:**\n \n- Callers can adjust the defaults using `NewConnectionWithOptions` or\nthe lower-level `spdy.NewFramerWithOptions` with functional options:\n`WithMaxControlFramePayloadSize`, `WithMaxHeaderFieldSize`, and\n`WithMaxHeaderCount`.\n ",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/moby/spdystream"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.5.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.5.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/moby/spdystream/security/advisories/GHSA-pc3f-x583-g7j2"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-35469"
}, {
"type" : "WEB",
"url" : "https://github.com/moby/spdystream/commit/ef6121f62c730110bf5ae604a865a8613bfb787f"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/moby/spdystream"
}, {
"type" : "WEB",
"url" : "https://github.com/moby/spdystream/releases/tag/v0.5.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-770" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-16T20:44:01Z",
"nvd_published_at" : "2026-04-16T22:16:37Z"
}
}