CVE-2026-35469

MEDIUMPre-NVD 6.58.7▲
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 91% 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, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.5Exploit: NoneExposed: 0

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
8.7(medium)
EPSS
47.1%
KEV
Not listed

Published

April 16, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Apr 29, 2026
Patch available. Sources: github.
github Patch Available

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(23)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-sriov-network-webhook-rhel9:17799155262026-06-11redhat
redhatopenshift4/ose-sriov-network-webhook:17797164762026-06-04redhat
redhatopenshift4/ose-sriov-network-webhook:17798643812026-06-04redhat
redhatopenshift4/ose-sriov-network-webhook-rhel9:17797800222026-06-03redhat
redhatopenshift4/ose-node-feature-discovery-rhel9:17792513412026-05-29redhat
redhatopenshift4/ose-sriov-network-webhook-rhel9:17792498012026-05-27redhat
redhatopenshift4/ose-powervs-block-csi-driver-rhel9:17792516842026-05-27redhat
redhatopenshift4/ose-powervs-block-csi-driver-rhel9:17792504272026-05-26redhat
redhatopenshift4/ose-powervs-block-csi-driver-rhel9:17787078842026-05-20redhat
redhatopenshift4/ose-node-feature-discovery-rhel9:17785214512026-05-20redhat
redhatopenshift4/ose-node-feature-discovery-rhel9:17785221022026-05-20redhat
redhatopenshift4/ose-powervs-block-csi-driver-rhel9:17781383372026-05-20redhat
redhatopenshift4/ose-node-feature-discovery-rhel9:17787010222026-05-20redhat
redhatopenshift4/ose-node-feature-discovery-rhel9:17781648722026-05-19redhat
redhatmulticluster-engine/assisted-service-9-rhel9:17791354782026-05-19redhat
redhatmulticluster-engine/assisted-service-9-rhel9:17788923702026-05-19redhat
redhatrhacm2/multicluster-operators-channel-rhel9:17783029212026-05-14redhat
redhatmulticluster-engine/assisted-service-9-rhel9:17782886462026-05-13redhat
redhatmulticluster-engine/assisted-service-8-rhel8:17782886552026-05-13redhat
redhatopenshift4/ose-powervs-block-csi-driver-rhel9:17770701082026-05-06redhat
redhatadvanced-cluster-security/rhacs-roxctl-rhel8:17779866302026-05-05redhat
redhatadvanced-cluster-security/rhacs-roxctl-rhel8:17779764892026-05-05redhat
redhatadvanced-cluster-security/rhacs-roxctl-rhel8:17773077912026-04-27redhat

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
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.

Data Freshness Timeline

(refreshed 8× in last 7d / 45× 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 112 total refreshes for this CVE.

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

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 in the National Vulnerability Database on April 16, 2026, with the most recent update on July 10, 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 47.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-35469?
CVE-2026-35469 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7.
How do I remediate CVE-2026-35469?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35469, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs