CVE-2025-64329Medium

Microsoft security update for CVE-2025-64329

Published
May 31, 2026
Last Modified
—

🔗 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-2025-64329. This page also shows what EchelonGraph holds for CVE-2025-64329, 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.0.0-14 on Azure Linux 3.0
  • azl3 containerd2 2.0.0-16 on Azure Linux 3.0
  • azl3 moby-containerd-cc 1.7.7-9 on Azure Linux 3.0
  • cbl2 moby-containerd 1.6.26-12 on CBL Mariner 2.0
  • cbl2 moby-containerd-cc 1.7.7-12 on CBL Mariner 2.0

✅ Updates Microsoft lists: 5 updates

5 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update2.0.0-15
—Security Update2.0.0-16
—Security Update1.7.7-10
—Security Update1.6.26-13
—Security Update1.7.7-13

🧭 EchelonGraph on CVE-2025-64329

EchelonGraph score
5.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

containerd is an open-source container runtime. Versions 1.7.28 and below, 2.0.0-beta.0 through 2.0.6, 2.1.0-beta.0 through 2.1.4, and 2.2.0-beta.0 through 2.2.0-rc.1 contain a bug in the CRI Attach implementation where a user can exhaust memory on the host due to goroutine leaks. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. To workaround this vulnerability, users can set up an admission controller to control accesses to pods/attach resources.

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2025-64329, 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).

🔗 References (2)