Microsoft security update for CVE-2026-35469 — azl3
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-35469. This page also shows what EchelonGraph holds for CVE-2026-35469, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products11
- azl3 cert-manager 1.12.15-6 on Azure Linux 3.0
- azl3 containerd2 0.0.0-1 on Azure Linux 3.0
- azl3 containerized-data-importer 1.62.0-3 on Azure Linux 3.0
- azl3 cri-tools 1.32.0-4 on Azure Linux 3.0
- azl3 docker-buildx 0.14.0-11 on Azure Linux 3.0
- azl3 docker-compose 2.27.0-9 on Azure Linux 3.0
- azl3 keda 2.14.1-11 on Azure Linux 3.0
- azl3 kubernetes 1.30.10-23 on Azure Linux 3.0
- azl3 kubevirt 1.7.1-2 on Azure Linux 3.0
- azl3 kured 1.15.0-3 on Azure Linux 3.0
- azl3 moby-containerd-cc 1.7.7-11 on Azure Linux 3.0
✅ Updates Microsoft lists: 11 updates
11 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 2.0.0-19 |
| — | Security Update | 1.12.15-7 |
| — | Security Update | 1.62.0-4 |
| — | Security Update | 1.32.0-5 |
| — | Security Update | 0.14.0-12 |
| — | Security Update | 2.27.0-10 |
| — | Security Update | 2.14.1-12 |
| — | Security Update | 1.30.10-23 |
| — | Security Update | 1.7.1-3 |
| — | Security Update | 1.15.0-4 |
| — | Security Update | 1.7.7-12 |
🧭 EchelonGraph on CVE-2026-35469
- EchelonGraph score
- 6.5 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2026-35469, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).