How severe is CVE-2025-64329?

No CVSS score has been assigned to CVE-2025-64329 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-64329?

CVE-2025-64329 affects the following packages: github.com/containerd/containerd (Go), github.com/containerd/containerd/v2 (Go), github.com/containerd/containerd/v2 (Go), github.com/containerd/containerd/v2 (Go). Ecosystems affected: Go.

How do I fix CVE-2025-64329?

Update github.com/containerd/containerd to 1.7.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64329 is resolved across your whole dependency graph.

How do I detect CVE-2025-64329 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containerd/containerd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-64329 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-64329?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-64329 can be triaged on real exposure rather than presence alone.

Is CVE-2025-64329 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-64329 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-64329?

CVE-2025-64329 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 6th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-64329?

CVE-2025-64329 is classified as CWE-401 (CWE-401). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-64329 published, and has it been updated?

CVE-2025-64329 was published on November 7, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-64329 — containerd

Fix: containerd/containerd@083b53c

CVE-2025-64329 is a CWE-401 vulnerability in github.com/containerd/containerd. A fix is available for github.com/containerd/containerd — see the affected versions and patch details below.

containerd CRI server: Host memory exhaustion through Attach goroutine leak

Also known asGHSA-m6hq-p25p-ffr2GO-2025-4108

Published

Nov 7, 2025

Updated

Aug 12, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64329.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs6th percentile — riskier than 6% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

4 pkgs affected

🐹github.com/containerd/containerd🐹github.com/containerd/containerd/v2🐹github.com/containerd/containerd/v2🐹github.com/containerd/containerd/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/containerd/containerd`	all versions	1.7.29`go get github.com/containerd/containerd@v1.7.29`
🐹Go	`github.com/containerd/containerd/v2`	all versions	2.0.7`go get github.com/containerd/containerd/v2@v2.0.7`
🐹Go	`github.com/containerd/containerd/v2`	≥ 2.1.0-beta.0&&< 2.1.5	2.1.5`go get github.com/containerd/containerd/v2@v2.1.5`
🐹Go	`github.com/containerd/containerd/v2`	≥ 2.2.0-beta.0&&< 2.2.0	2.2.0`go get github.com/containerd/containerd/v2@v2.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containerd/containerd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/containerd/containerd to 1.7.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64329 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-64329 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-64329. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

The highest threat of this vulnerability is to system availability. A flaw in containerd's CRI Attach implementation allows a user to exhaust memory on the host due to goroutine leaks, leading to a denial of service.

Product	Fixed in	Advisory
Network Observability (NETOBSERV) 1.11.0	`network-observability/network-observability-cli-rhel9:1771226060`	RHSA-2026:2900
Red Hat Openshift Data Foundation 4.22	`odf4/cephcsi-rhel9:1782932114`	RHSA-2026:37387

UbuntuMEDIUM

USN-7983-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-64329 in your dependencies?

O3 Security finds CVE-2025-64329 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works