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.
CVE-2026-35469
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 49%
- KEV
- Not listed
Published
April 16, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Apr 29, 2026Memory amplification in SPDY frame parsing leads to denial of service · Advisory · moby/spdystream · GitHub
https://github.com/moby/spdystream/security/advisories/GHSA-pc3f-x583-g7j2Release v0.5.1 · moby/spdystream · GitHub
https://github.com/moby/spdystream/releases/tag/v0.5.1Vendor Advisories for CVE-2026-35469(20)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:56431Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.18.27 security, enhancement & bug fix update
- RHSA-2026:51007Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.19.42 bug fix and security update
- RHSA-2026:51013Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.18.52 bug fix and security update
- RHSA-2026:51422Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of MicroShift 4.19.42 security update
- RHSA-2026:53655Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Virtualization v4.13 Images
- RHSA-2026:51022Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.20.33 bug fix and security update
- RHSA-2026:47728Red Hat Product SecurityCritical
Red Hat Security Advisory: OpenShift Container Platform 4.17.56 bug fix and security update
- RHSA-2026:47729Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.17.56 security and extras update
- +12 more
Patch Availability(30)
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-github-docker-spdystream | 0.2.0-1, 0.5.0-1 | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-github-docker-spdystream | 0.2.0-1, 0.5.0-1 | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-github-docker-spdystream | 0.5.0-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-github-docker-spdystream | 0.5.0-1 | — | — |
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/moby/spdystream | — | 0.5.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(25)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
- Microsoft MSRCCVE-2026-354692026-04-17
SpdyStream: DOS on CRI
- Red HatRHSA-2026:11070IMPORTANT2026-04-13
RHSA-2026:11070 — Important
- Red HatRHSA-2026:11217IMPORTANT2026-04-13
RHSA-2026:11217 — Important
- Red HatRHSA-2026:12118IMPORTANT2026-04-13
RHSA-2026:12118 — Important
- Red HatRHSA-2026:13791IMPORTANT2026-04-13
RHSA-2026:13791 — Important
- Red HatRHSA-2026:13829IMPORTANT2026-04-13
RHSA-2026:13829 — Important
- Red HatRHSA-2026:17121IMPORTANT2026-04-13
RHSA-2026:17121 — Important
- Red HatRHSA-2026:17123IMPORTANT2026-04-13
RHSA-2026:17123 — Important
- Red HatRHSA-2026:17449IMPORTANT2026-04-13
RHSA-2026:17449 — Important
- Red HatRHSA-2026:17468IMPORTANT2026-04-13
RHSA-2026:17468 — Important
- Red HatRHSA-2026:17469IMPORTANT2026-04-13
RHSA-2026:17469 — Important
- Red HatRHSA-2026:17475IMPORTANT2026-04-13
RHSA-2026:17475 — Important
- Red HatRHSA-2026:17598IMPORTANT2026-04-13
RHSA-2026:17598 — Important
- Red HatRHSA-2026:17599IMPORTANT2026-04-13
RHSA-2026:17599 — Important
- Red HatRHSA-2026:17704IMPORTANT2026-04-13
RHSA-2026:17704 — Important
- Red HatRHSA-2026:19099IMPORTANT2026-04-13
RHSA-2026:19099 — Important
- Red HatRHSA-2026:19108IMPORTANT2026-04-13
RHSA-2026:19108 — Important
- Red HatRHSA-2026:20034IMPORTANT2026-04-13
RHSA-2026:20034 — Important
- Red HatRHSA-2026:20041IMPORTANT2026-04-13
RHSA-2026:20041 — Important
- Red HatRHSA-2026:20042IMPORTANT2026-04-13
RHSA-2026:20042 — Important
- Red HatRHSA-2026:20089IMPORTANT2026-04-13
RHSA-2026:20089 — Important
- Red HatRHSA-2026:21658IMPORTANT2026-04-13
RHSA-2026:21658 — Important
- Red HatRHSA-2026:21692IMPORTANT2026-04-13
RHSA-2026:21692 — Important
- Red HatRHSA-2026:21697IMPORTANT2026-04-13
RHSA-2026:21697 — Important
- Red HatRHSA-2026:23235IMPORTANT2026-04-13
RHSA-2026:23235 — Important
Data Freshness Timeline
(refreshed 21× in last 7d / 113× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 235 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 13:25 UTCEG score recompute
- 2026-08-25 13:25 UTCVendor advisory
- 2026-08-25 12:21 UTCEG score recompute
- 2026-08-25 12:21 UTCVendor advisory
- 2026-08-24 13:31 UTCEG score recompute
- 2026-08-24 13:31 UTCVendor advisory
- 2026-08-24 12:26 UTCEG score recompute
- 2026-08-24 12:26 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 13:59 UTCEG score recompute
- 2026-08-20 13:59 UTCVendor advisory
- 2026-08-20 12:45 UTCEG score recompute
- 2026-08-20 12:45 UTCVendor advisory
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 12:27 UTCEG score recompute
- 2026-08-19 12:27 UTCVendor advisory
- 2026-08-19 12:11 UTCEG score recompute
- 2026-08-19 12:11 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 12:21 UTCEG score recompute
- 2026-08-18 12:21 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-17 12:20 UTCEG score recompute
- 2026-08-17 12:20 UTCVendor advisory
- 2026-08-17 12:13 UTCEG score recompute
- 2026-08-17 12:13 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:34 UTCEG score recompute
- 2026-08-16 06:34 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 13:28 UTCEG score recompute
- 2026-08-14 13:28 UTCVendor advisory
- 2026-08-14 12:29 UTCEG score recompute
- 2026-08-14 12:29 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 13:38 UTCEG score recompute
- 2026-08-13 13:38 UTCVendor advisory
- 2026-08-13 12:29 UTCEG score recompute
- 2026-08-13 12:29 UTCVendor advisory
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 12:38 UTCEG score recompute
- 2026-08-12 12:38 UTCVendor advisory
- 2026-08-12 12:13 UTCEG score recompute
- 2026-08-12 12:13 UTCVendor advisory
- 2026-08-11 13:23 UTCEG score recompute
- 2026-08-11 13:23 UTCVendor advisory
- 2026-08-11 12:24 UTCEG score recompute
- 2026-08-11 12:24 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 13:22 UTCEG score recompute
- 2026-08-10 13:22 UTCVendor advisory
- 2026-08-10 12:27 UTCEG score recompute
- 2026-08-10 12:27 UTCVendor advisory
- 2026-08-10 04:26 UTCEG score recompute
- 2026-08-10 04:26 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 03:56 UTCEG score recompute
- 2026-08-09 03:56 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 14:09 UTCEG score recompute
- 2026-08-07 14:09 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 13:39 UTCEG score recompute
- 2026-08-06 13:39 UTCVendor advisory
- 2026-08-06 12:34 UTCEG score recompute
- 2026-08-06 12:34 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 13:52 UTCEG score recompute
- 2026-08-05 13:52 UTCVendor advisory
- 2026-08-05 12:40 UTCEG score recompute
- 2026-08-05 12:40 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 13:27 UTCEG score recompute
- 2026-08-04 13:27 UTCVendor advisory
- 2026-08-04 12:34 UTCEG score recompute
- 2026-08-04 12:34 UTCVendor advisory
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 13:43 UTCEG score recompute
- 2026-08-03 13:43 UTCVendor advisory
- 2026-08-03 12:48 UTCEG score recompute
- 2026-08-03 12:48 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 13:09 UTCEG score recompute
- 2026-08-02 13:09 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 13:22 UTCEG score recompute
- 2026-07-31 13:22 UTCVendor advisory
- 2026-07-31 12:35 UTCEG score recompute
- 2026-07-31 12:35 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 12:25 UTCEG score recompute
- 2026-07-30 12:25 UTCVendor advisory
- 2026-07-30 12:09 UTCEG score recompute
- 2026-07-30 12:09 UTCVendor advisory
- 2026-07-30 01:30 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p95HIGH
Same CWE
10 shownCWE-770
Frequently asked(5)
What is CVE-2026-35469?
When was CVE-2026-35469 disclosed?
Is CVE-2026-35469 actively exploited?
What is the CVSS score of CVE-2026-35469?
How do I remediate CVE-2026-35469?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-35469
Is Your Infrastructure Affected by CVE-2026-35469?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.