Microsoft security update for CVE-2026-53495 — 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-53495. This page also shows what EchelonGraph holds for CVE-2026-53495, 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 products5
- azl3 containerd2 2.2.4-8 on Azure Linux 3.0
- azl3 containerd2 2.3.4-1 on Azure Linux 3.0
- azl3 moby-containerd-cc 1.7.7-16 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
✅ Updates Microsoft lists: 4 updates
4 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 | 2.3.4-1 |
| — | Security Update | 1.7.7-19 |
| — | Security Update | 2.3.7-1 |
🧭 EchelonGraph on CVE-2026-53495
- EchelonGraph score
- 6.8 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 on Linux with the CRI plugin enabled can indefinitely block the drainExecSyncIO goroutine in internal/cri/server/container_execsync.go when CRI ExecSync is used by exec probes or lifecycle hooks that launch long-lived background child processes retaining standard input and output pipes. The input and output drain phase has no default timeout and did not stop when the request context was canceled, so repeated ExecSync invocations can accumulate blocked goroutines and host memory. The resulting resource exhaustion can cause the OOM killer to terminate containerd, leaving the container runtime unavailable until restart. Deployments not using containerd's CRI implementation and containers not running on Linux are not affected. 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-53495, 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).