Microsoft security update for CVE-2026-85091 — 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-85091. This page also shows what EchelonGraph holds for CVE-2026-85091, 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 products9
- azl3 cloud-hypervisor 52.0.152-1 on Azure Linux 3.0
- azl3 cloud-hypervisor 52.0.187-1 on Azure Linux 3.0
- azl3 kata-containers 3.32.0.kata0-2 on Azure Linux 3.0
- azl3 kata-containers 3.32.0.kata0-5 on Azure Linux 3.0
- azl3 kata-containers 4.1.0.kata0-1 on Azure Linux 3.0
- azl3 kata-containers 4.1.0.kata1-2 on Azure Linux 3.0
- azl3 kata-containers 4.1.0.kata2-1 on Azure Linux 3.0
- azl3 zlib 1.3.2-1 on Azure Linux 3.0
- azl3 zlib 1.3.2-2 on Azure Linux 3.0
✅ Updates Microsoft lists: 3 updates
3 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 | — |
| — | Security Update | 1.3.2-2 |
| — | Security Update | — |
🧭 EchelonGraph on CVE-2026-85091
- EchelonGraph score
- 7.4 HIGH
- 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
zlib 1.2.11 through 1.3.2 contains a heap buffer overflow: after an underlying write() fails, gz_write() returns without resetting strm.next_in, leaving it pointed at the caller's buffer. A later gz* write call then derives a position from the stale pointer and writes past a heap allocation; any write() failure reaches it, including EPIPE on a blocking descriptor, and in versions before 1.3.1.2 the failed write must be followed by a gzclearerr() call.
Published by VulnCheck, the CVE Numbering Authority that assigned CVE-2026-85091, 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).