CVE-2025-64329 | containerd CRI server: Host memory exhaustion through Attach goroutine leak

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: 2025-11-07 Last update: 2025-12-31 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-64329 is rated Low Risk (28.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-64329

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-07 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-64329

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.9 4.0 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Click to expand
Attack vector (AV:L)
Attacker needs local access on the target system.
Attack complexity (AC:L)
Exploitation conditions are straightforward and stable.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:N)
No privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:N)
No confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:N)
No integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N)
No availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:X)
Not evaluated.
Recovery (supplemental) (R:X)
Not evaluated.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:X)
Not evaluated.
Provider urgency (supplemental) (U:X)
Not evaluated.
 — — [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2025-64329

GitHub Security Advisory for CVE-2025-64329

GHSA-m6hq-p25p-ffr2 · Severity: medium · Ecosystem: go — containerd CRI server: Host memory exhaustion through Attach goroutine leak

OS Trackers for CVE-2025-64329

vendor priority summary link
alpine — CVE-2025-64329: 1 source package rows (containerd); 67 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 0, open 67. https://security.alpinelinux.org/vuln/CVE-2025-64329
debian not yet assigned CVE-2025-64329 not yet assigned priority: Debian including 1 source packages (containerd), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-64329
redhat medium — https://access.redhat.com/security/cve/CVE-2025-64329
suse medium CVE-2025-64329 severity moderate: SUSE including 246 source package names (amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, amazon/suse-sles-15-sp1-chost-byos-v20220127-hvm-ssd-x86_64, …), 521 product×package rows across 219 product lines (Container suse/sl-micro/6.0/toolbox, Image SL-Micro-Azure, … (219 product lines)): Fixed 290, Known Affected 231. https://www.suse.com/security/cve/CVE-2025-64329/
ubuntu medium CVE-2025-64329 medium priority: Ubuntu including 2 source packages (containerd, containerd-app), 14 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): released 10, ignored 2, needs-triage 2. https://ubuntu.com/security/CVE-2025-64329

Affected software / configurations for CVE-2025-64329

Vendor Product Version Raw CPE
linuxfoundation containerd < 1.7.29 cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
linuxfoundation containerd >= 2.0.0, < 2.0.7 cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
linuxfoundation containerd >= 2.1.0, < 2.1.5 cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
linuxfoundation containerd 2.2.0 cpe:2.3:a:linuxfoundation:containerd:2.2.0:beta0:*:*:*:*:*:*
linuxfoundation containerd 2.2.0 cpe:2.3:a:linuxfoundation:containerd:2.2.0:beta1:*:*:*:*:*:*
linuxfoundation containerd 2.2.0 cpe:2.3:a:linuxfoundation:containerd:2.2.0:beta2:*:*:*:*:*:*
linuxfoundation containerd 2.2.0 cpe:2.3:a:linuxfoundation:containerd:2.2.0:rc0:*:*:*:*:*:*
linuxfoundation containerd 2.2.0 cpe:2.3:a:linuxfoundation:containerd:2.2.0:rc1:*:*:*:*:*:*

References for CVE-2025-64329

cvelogic Threat Intelligence