CVE-2025-64329

Workarounds

Set up an admission controller to control accesses to pods/attach resources.
e.g., Validating Admission Policy.

Credits

The containerd project would like to thank @Wheat2018 for responsibly disclosing this issue in accordance with the containerd security policy.

References

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-64329

For more information

If you have any questions or comments about this advisory:

• Open an issue in containerd
• Email us at [email protected]

To report a security issue in containerd:

• Report a new vulnerability

A bug was found in containerd's CRI Attach implementation where a user can exhaust memory on the host due to goroutine leaks.

Repetitive calls of CRI Attach (e.g., kubectl attach) could increase the memory usage of containerd.

Kodem intelligence

This bug has been fixed in the following containerd versions:

• 2.2.0
• 2.1.5
• 2.0.7
• 1.7.29

Users should update to these versions to resolve the issue.

1. What is CVE-2025-64329? CVE-2025-64329 is a medium-severity security vulnerability in github.com/containerd/containerd (go), affecting versions < 1.7.29. It is fixed in 1.7.29, 2.0.7, 2.1.5, 2.2.0.
2. Which packages are affected by CVE-2025-64329?
   • github.com/containerd/containerd (go) (versions < 1.7.29)
   • github.com/containerd/containerd/v2 (go) (versions < 2.0.7)
3. Is there a fix for CVE-2025-64329? Yes. CVE-2025-64329 is fixed in 1.7.29, 2.0.7, 2.1.5, 2.2.0. Upgrade to this version or later.
4. Is CVE-2025-64329 exploitable, and should I be worried? Whether CVE-2025-64329 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2025-64329 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2025-64329?
   • Upgrade github.com/containerd/containerd to 1.7.29 or later
   • Upgrade github.com/containerd/containerd/v2 to 2.0.7 or later
   • Upgrade github.com/containerd/containerd/v2 to 2.1.5 or later
   • Upgrade github.com/containerd/containerd/v2 to 2.2.0 or later