🛡️ CVE-2025-64329 — containerd
Description
containerd CRI server: Host memory exhaustion through Attach goroutine leak
Impact
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](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_attach/)) could increase the memory usage of containerd.
Patches
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.
Workarounds
Set up an admission controller to control accesses to pods/attach resources.
e.g., [Validating Admission Policy](https://kubernetes.io/docs/reference/access-authn-authz/validating-admission-policy/).
Credits
The containerd project would like to thank @Wheat2018 for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md).
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](https://github.com/containerd/containerd/issues/new/choose)
- Email us at [[email protected]](mailto:[email protected])
To report a security issue in containerd:
- [Report a new vulnerability](https://github.com/containerd/containerd/security/advisories/new)
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
Weakness class
CVE-2025-64329 is classified as CWE-401: Memory Leak. Allocated memory is never released, so long-running or repeated operations gradually exhaust it.
Affected software
CVE-2025-64329 is recorded against 3 packages.
- containerd
- github.com/containerd/containerd
- github.com/containerd/containerd/v2
Timeline and source
Published on 7 November 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.
References
CVE-2025-64329 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| containerd | — | — |
| github.com/containerd/containerd | — | — |
| github.com/containerd/containerd/v2 | — | — |
References
Similar Threats
- Unknown BELL-CVE-2026-25680
- Unknown BELL-CVE-2026-25681
- Unknown BELL-CVE-2026-27136
- Unknown BELL-CVE-2026-39821
- Unknown BELL-CVE-2026-39827
More CVE 2025 advisories
Browse all of CVE 2025 in the advisory index.
Vulnerability Monitoring
Track new vulnerabilities in containerd
CVE-2025-64329 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.