Microsoft security update for CVE-2026-95838 — 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-95838. This page also shows what EchelonGraph holds for CVE-2026-95838, 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 products12
- azl3 containerd2 2.3.4-1 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 kata-containers-cc 3.15.0.aks0-21 on Azure Linux 3.0
- azl3 kata-containers-cc 3.15.0.aks0-23 on Azure Linux 3.0
- azl3 kata-containers-cc 3.15.0.aks0-24 on Azure Linux 3.0
- azl3 moby-containerd-cc 1.7.7-17 on Azure Linux 3.0
- azl3 moby-containerd-cc 1.7.7-19 on Azure Linux 3.0
- azl3 moby-engine 25.0.18-1 on Azure Linux 3.0
- azl3 moby-engine 25.0.18-2 on Azure Linux 3.0
- azl3 moby-engine 25.0.3-20 on Azure Linux 3.0
✅ Updates Microsoft lists: 7 updates
7 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 | 1.7.7-19 |
| — | Security Update | 2.3.7-1 |
| — | Security Update | — |
| — | Security Update | 4.1.0.kata1-3 |
| — | Security Update | 3.15.0.aks0-24 |
| — | Security Update | 25.0.18-2 |
| — | Security Update | 4.1.0.kata2-1 |
🧭 EchelonGraph on CVE-2026-95838
- EchelonGraph score
- 4.6 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
containerd is an open-source container runtime. Prior to 1.7.35, 2.0.12, 2.2.8, and 2.3.5, containerd's layer unpack handler repeatedly traverses directories for certain opaque whiteout configurations. A malicious image layer can trigger repeated directory traversals while opaque whiteouts are processed. Pulling or importing the image can consume CPU, delay container startup, and reduce image-pull concurrency for unrelated deployments. This issue is fixed in versions 1.7.35, 2.0.12, 2.2.8, and 2.3.5.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2026-95838, 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).