CVE-2026-35469

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

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 computed
Severity65% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

Published

April 16, 2026

Last Modified

September 11, 2026

Advisory Details (2)

Auto-updated Apr 29, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Memory amplification in SPDY frame parsing leads to denial of service · Advisory · moby/spdystream · GitHub

https://github.com/moby/spdystream/security/advisories/GHSA-pc3f-x583-g7j2
generic

Release v0.5.1 · moby/spdystream · GitHub

https://github.com/moby/spdystream/releases/tag/v0.5.1

Vendor 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.

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-logging/cluster-logging-rhel9-operator:17884395052026-09-10redhat
redhatopenshift4/ose-hypershift-rhel9:17882782602026-09-08redhat
redhatopenshift4/ose-ovn-kubernetes-rhel9:17875602462026-09-03redhat
redhatcluster-observability-operator/cluster-observability-rhel9-operator:17875936372026-08-31redhat
redhatmulticluster-engine/image-based-install-rhel9:17865489182026-08-25redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatopenshift4/ose-ovn-kubernetes-rhel9:17856553902026-08-12redhat
redhatopenshift4/ose-ovn-kubernetes-rhel9:17856007922026-08-12redhat
redhatmicroshift-0:4.19.42-202608062155.p0.g46c9d67.assembly.4.19.42.el92026-08-12redhat
redhatcontainer-native-virtualization/virt-exportserver-rhel9:17863466202026-08-11redhat
redhatopenshift4/ose-ovn-kubernetes-rhel9:17858575302026-08-11redhat
redhatopenshift4/ose-csi-external-provisioner-rhel9:17843192182026-08-06redhat
redhatopenshift4/ose-aws-ebs-csi-driver-rhel9:17843135422026-08-06redhat
redhatopenshift4/ose-openshift-apiserver-rhel9:17845769332026-07-30redhat
redhatopenshift4/ose-openshift-apiserver-rhel8:17845823772026-07-30redhat
redhatopenshift4/ose-ovn-kubernetes-microshift-rhel9:17847023982026-07-28redhat
redhatopenshift4/ose-ovn-kubernetes-microshift-rhel9:17845486262026-07-28redhat
redhatopenshift4/ose-openshift-apiserver-rhel8:17840547952026-07-23redhat
redhatopenshift4/ose-openshift-apiserver-rhel8:17840562552026-07-23redhat
redhatopenshift4/ose-node-feature-discovery:17840557262026-07-23redhat
redhatopenshift4/ose-aws-ebs-csi-driver-rhel9:17837028672026-07-22redhat
redhatflightctl-0:1.1.3-1.el9em2026-07-16redhat
redhatopenshift4/ose-openshift-apiserver-rhel9:17829042342026-07-16redhat
redhatopenshift4/ose-aws-ebs-csi-driver-rhel9:17833581812026-07-15redhat
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel9:17830884462026-07-15redhat
redhatopenshift4/ose-csi-external-provisioner-rhel9:17830843082026-07-15redhat
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel9:17830904882026-07-14redhat
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel9:17834199852026-07-14redhat
redhatopenshift4/ose-node-feature-discovery:17823954162026-07-09redhat
redhatopenshift-0:4.19.0-202606301915.p2.g63adf01.assembly.stream.el92026-07-09redhat

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)
PackageVulnerable rangeFix by version rangeDependents
golang-github-docker-spdystream0.2.0-1, 0.5.0-1
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-docker-spdystream0.2.0-1, 0.5.0-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-docker-spdystream0.5.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-docker-spdystream0.5.0-1
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/moby/spdystream—
  • every version up to 0.5.1: fixed in 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.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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 304 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:42 UTCEPSS rescore
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-01 19:49 UTCEPSS rescore
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-30 07:28 UTCOSV refresh
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-17 19:30 UTCEPSS rescore
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 03:11 UTCEPSS rescore
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-12 15:01 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 13:25 UTCEG score recompute
  25. 2026-09-11 13:25 UTCVendor advisory
Show 75 more
  1. 2026-09-11 12:21 UTCEG score recompute
  2. 2026-09-11 12:21 UTCVendor advisory
  3. 2026-09-11 09:37 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-09 13:41 UTCEG score recompute
  6. 2026-09-09 13:41 UTCVendor advisory
  7. 2026-09-09 12:40 UTCEG score recompute
  8. 2026-09-09 12:40 UTCVendor advisory
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-07 14:00 UTCEG score recompute
  12. 2026-09-07 14:00 UTCVendor advisory
  13. 2026-09-07 13:14 UTCEG score recompute
  14. 2026-09-07 13:14 UTCVendor advisory
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 13:29 UTCEG score recompute
  17. 2026-09-04 13:29 UTCVendor advisory
  18. 2026-09-04 12:23 UTCEG score recompute
  19. 2026-09-04 12:23 UTCVendor advisory
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 13:53 UTCEPSS rescore
  23. 2026-09-01 13:50 UTCEG score recompute
  24. 2026-09-01 13:50 UTCVendor advisory
  25. 2026-09-01 12:22 UTCEG score recompute
  26. 2026-09-01 12:22 UTCVendor advisory
  27. 2026-09-01 04:39 UTCEPSS rescore
  28. 2026-08-31 13:34 UTCEG score recompute
  29. 2026-08-31 13:34 UTCVendor advisory
  30. 2026-08-31 12:31 UTCEG score recompute
  31. 2026-08-31 12:31 UTCVendor advisory
  32. 2026-08-30 19:17 UTCEPSS rescore
  33. 2026-08-30 01:22 UTCEPSS rescore
  34. 2026-08-28 21:41 UTCEPSS rescore
  35. 2026-08-27 14:25 UTCEPSS rescore
  36. 2026-08-27 13:35 UTCEG score recompute
  37. 2026-08-27 13:35 UTCVendor advisory
  38. 2026-08-27 13:02 UTCEG score recompute
  39. 2026-08-27 13:02 UTCVendor advisory
  40. 2026-08-26 16:12 UTCEG score recompute
  41. 2026-08-26 16:12 UTCVendor advisory
  42. 2026-08-26 14:46 UTCEPSS rescore
  43. 2026-08-26 12:23 UTCEG score recompute
  44. 2026-08-26 12:23 UTCVendor advisory
  45. 2026-08-25 13:49 UTCEPSS rescore
  46. 2026-08-25 13:25 UTCEG score recompute
  47. 2026-08-25 13:25 UTCVendor advisory
  48. 2026-08-25 12:21 UTCEG score recompute
  49. 2026-08-25 12:21 UTCVendor advisory
  50. 2026-08-24 13:31 UTCEG score recompute
  51. 2026-08-24 13:31 UTCVendor advisory
  52. 2026-08-24 12:26 UTCEG score recompute
  53. 2026-08-24 12:26 UTCVendor advisory
  54. 2026-08-23 00:19 UTCEPSS rescore
  55. 2026-08-21 23:49 UTCEPSS rescore
  56. 2026-08-20 22:55 UTCEPSS rescore
  57. 2026-08-20 13:59 UTCEG score recompute
  58. 2026-08-20 13:59 UTCVendor advisory
  59. 2026-08-20 12:45 UTCEG score recompute
  60. 2026-08-20 12:45 UTCVendor advisory
  61. 2026-08-19 17:03 UTCEPSS rescore
  62. 2026-08-19 12:27 UTCEG score recompute
  63. 2026-08-19 12:27 UTCVendor advisory
  64. 2026-08-19 12:11 UTCEG score recompute
  65. 2026-08-19 12:11 UTCVendor advisory
  66. 2026-08-18 13:48 UTCEPSS rescore
  67. 2026-08-18 12:21 UTCEG score recompute
  68. 2026-08-18 12:21 UTCVendor advisory
  69. 2026-08-17 13:47 UTCEPSS rescore
  70. 2026-08-17 12:20 UTCEG score recompute
  71. 2026-08-17 12:20 UTCVendor advisory
  72. 2026-08-17 12:13 UTCEG score recompute
  73. 2026-08-17 12:13 UTCVendor advisory
  74. 2026-08-16 14:56 UTCEPSS rescore
  75. 2026-08-16 06:34 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-35469?
CVE-2026-35469 is a medium vulnerability published on April 16, 2026. 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…
When was CVE-2026-35469 disclosed?
CVE-2026-35469 was first published on April 16, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35469 actively exploited?
CVE-2026-35469 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-35469?
CVE-2026-35469 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-35469?
A fix for CVE-2026-35469 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-35469 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-35469

Explore →

Is Your Infrastructure Affected by CVE-2026-35469?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs