CVE-2026-35469
SpdyStream: DOS on CRI
CVE-2026-35469 is fixed in 13 products on 1 platform, first by RHSA-2026:41019, released May 22, 2026. It is not reported as exploited. Patch Radar priority: High.
High
CVSS
8.1
Important
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0066
51st percentile
github.com/moby/spdystream: memory amplification in SPDY frame parsing leads to denial of service
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| containerd · opensuse-leap 16.0 | 1.7.33-160000.1.1 | OPENSUSE-SU-2026:21213-1 | Jul 2, 2026 |
| containerd · sles 15.7 | 1.7.29-150000.142.1 | SUSE-SU-2026:3450-1 | Aug 3, 2026 |
| containerized-data-importer1.65 · opensuse-leap 16.0 | 1.65.0-160000.3.1 | OPENSUSE-SU-2026:21824-1 | Sep 9, 2026 |
| flightctl · RHEL 10 | 1.1.3-1.el10em | RHSA-2026:41019 | May 22, 2026 |
| govulncheck-vulndb · opensuse-leap 16.0 | 0.0.20260723T184607-160000.1.1 | OPENSUSE-SU-2026:21483-1 | Jul 30, 2026 |
| kubernetes · sles 15.7 | 1.35.4-150600.13.34.1 | SUSE-SU-2026:2342-1 | Jun 10, 2026 |
| kubernetes-old · sles 15.7 | 1.33.11-150600.13.32.1 | SUSE-SU-2026:2460-1 | Jun 18, 2026 |
| kubernetes1.33 · Fedora 43 | 1.33.13-1.fc43 | FEDORA-2026-C2A89CCCA5 | Jun 12, 2026 |
| kubernetes1.33-client · Fedora 43 | 1.33.13-1.fc43 | FEDORA-2026-C2A89CCCA5 | Jun 12, 2026 |
| kubernetes1.33-kubeadm · Fedora 43 | 1.33.13-1.fc43 | FEDORA-2026-C2A89CCCA5 | Jun 12, 2026 |
| kubernetes1.33-systemd · Fedora 43 | 1.33.13-1.fc43 | FEDORA-2026-C2A89CCCA5 | Jun 12, 2026 |
| kubevirt · sles 15.7 | 1.7.4-150700.3.30.1 | SUSE-SU-2026:3203-1 | Jul 23, 2026 |
| kubevirt-1.6 · sles 15.7 | 1.6.6-150700.15.17.1 | SUSE-SU-2026:3630-1 | Aug 17, 2026 |
| kubevirt1.8 · opensuse-leap 16.0 | 1.8.4-160000.1.1 | OPENSUSE-SU-2026:21590-1 | Aug 18, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.