# CVE-2025-64329: containerd CRI server: Host memory exhaustion through Attach goroutine leak > Attackers can exhaust host memory via goroutine leaks in containerd's CRI Attach implementation, causing denial of service. - **Severity:** Medium 6.9 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Nov 2025 - **Updated:** 7 Nov 2025 - **Also known as:** AZL-69739, AZL-69745, AZL-69973, AZL-69976, BELL-CVE-2025-64329, CLEANSTART-2026-DK18368, CLEANSTART-2026-RB58878, DEBIAN-CVE-2025-64329, GHSA-m6hq-p25p-ffr2, GO-2025-4108, MINI-2xcx-q8gp-cw8w, MINI-3h9r-ppvf-vc3g, MINI-3r8c-q4h4-fg8v, MINI-3vxh-jfvj-vmq6, MINI-3xpm-gjh2-578g, MINI-42hg-gx2f-4wx9, MINI-4342-j5fx-39jh, MINI-48wm-grwf-fv24, MINI-499x-3cwq-h6p8, MINI-4c22-79w3-3f87, MINI-4g3v-9xgc-54h6, MINI-4jj2-3w84-jff2, MINI-5297-j7r8-4376, MINI-53w8-gxv9-jgxr, MINI-552r-5vgj-36qw, MINI-5pj7-7mhh-qgf7, MINI-6348-g93x-3crj, MINI-63w6-h6v7-q55x, MINI-69m2-2h6j-5wwx, MINI-6j7v-x399-4w53, MINI-72jc-jwwf-x3jj, MINI-786c-62fj-wq3v, MINI-78w9-fpxf-rjmp, MINI-7hxm-5439-gf64, MINI-7m2q-24x2-3vcc, MINI-7prh-r5c6-q3g2, MINI-7wrp-5jq2-6687, MINI-86mv-pccg-6gxm, MINI-874p-q2xv-hpv9, MINI-87xg-ggwj-mvmr, MINI-8c67-5x37-w7f5, MINI-8ch6-85hq-wwrw, MINI-8j8f-r64w-9wqf, MINI-8jr8-p9mc-qwv7, MINI-8pg2-gfgx-24rm, MINI-92p9-f3mp-9r78, MINI-9c3r-8389-hv8q, MINI-9gxw-cg54-829j, MINI-9m3r-cg98-45qv, MINI-c62w-rpf2-mpc5, MINI-c682-qq24-xw49, MINI-c6rq-fj3c-5gmc, MINI-c9v5-x7cm-w9mq, MINI-cqr8-cj9j-c297, MINI-f4f7-h3g4-445c, MINI-f5gc-jw8p-mwrx, MINI-f5mw-h448-vr9m, MINI-fwrw-xxhc-7h2w, MINI-g7fj-qf2q-895m, MINI-g9fq-vvf6-h4jj, MINI-ggj3-58m5-8vj6, MINI-j4q2-87mj-72cj, MINI-j563-fjxg-m9r3, MINI-j756-f2p6-8rvv, MINI-jw85-x8gj-r9pc, MINI-jx8j-2q39-8973, MINI-m57x-4c3h-jx36, MINI-m5rx-q3q4-7vgq, MINI-mfjx-58f8-vpgq, MINI-mq4v-jmmr-2xp3, MINI-p6x9-qxm8-jh58, MINI-pg56-g5f8-8j4m, MINI-pjwj-c63v-77fr, MINI-pqm5-g7q7-q7wc, MINI-prq6-2f7v-cv2r, MINI-prqh-3fw5-849w, MINI-q3wg-hrxr-c8m2, MINI-qgqv-5wch-v3gf, MINI-qv3r-55g5-h3fr, MINI-r53q-q945-mr6g, MINI-r5mh-8v3v-hg78, MINI-r78q-2fx4-fgh4, MINI-rvpx-jhcg-9g9f, MINI-rvwv-96r7-fvpx, MINI-rwcm-8j3c-v993, MINI-v6r8-pw7x-5jpj, MINI-v855-24p4-23hx, MINI-vq79-g63j-7728, MINI-vqr8-r9pw-6p4x, MINI-vxhc-pc3m-p5gf, MINI-w7h7-8qwp-w5hm, MINI-w8fp-wv48-mhg5, MINI-wjw7-7vx5-c8qc, MINI-wq7p-qpm3-j8c6, MINI-x6gg-29w3-jfcv, MINI-x8w8-w2qf-fwj8, MINI-xc59-pm9j-c22g, MINI-xgj2-c6p3-gmf8, MINI-xj8x-7833-3433, MINI-xjf4-g67c-cmvc, MINI-xxjw-5676-q8fh, UBUNTU-CVE-2025-64329 ## What is CVE-2025-64329? CVE-2025-64329 is a medium-severity denial of service vulnerability in containerd, published on 7 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime) ## Which versions are affected by CVE-2025-64329? 10 open source packages ship an affected version, including github.com/containerd/containerd/v2 and github.com/containerd/containerd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/containerd/containerd/v2` | Go | All versions | 2.0.7, 2.1.5, 2.2.0 | | `github.com/containerd/containerd/v2` | Go | All versions | 2.0.7 | | `github.com/containerd/containerd/v2` | Go | All versions | 2.0.7 | | `github.com/containerd/containerd/v2` | Go | From 2.1.0-beta.0 | 2.1.5 | | `github.com/containerd/containerd/v2` | Go | From 2.1.0-beta.0 | 2.1.5 | | `github.com/containerd/containerd/v2` | Go | From 2.2.0-beta.0 | 2.2.0 | | `github.com/containerd/containerd/v2` | Go | From 2.2.0-beta.0 | 2.2.0 | | `github.com/containerd/containerd` | Go | All versions | 1.7.29 | | `github.com/containerd/containerd` | Go | All versions | 1.7.29 | | `github.com/containerd/containerd` | Go | All versions | 1.7.29 | Products: Linuxfoundation Containerd. ## How do I fix CVE-2025-64329? Upgrade github.com/containerd/containerd/v2 to a fixed version for your release line: 2.0.7, 2.1.5 or 2.2.0. ## Is CVE-2025-64329 being exploited? There is no known exploitation of CVE-2025-64329 in the wild and no public exploit code. ## Other vulnerabilities in containerd - [CVE-2026-53488](https://insights.sbomify.com/CVE-2026-53488/): containerd CRI — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull (critical 9.4) - [CVE-2026-53492](https://insights.sbomify.com/CVE-2026-53492/): containerd CRI checkpoint restore CDI annotation smuggling (high 8.4) - [CVE-2026-53489](https://insights.sbomify.com/CVE-2026-53489/): containerd: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore (high 8.2) - [CVE-2025-47290](https://insights.sbomify.com/CVE-2025-47290/): Containerd vulnerable to host filesystem access during image unpack (high 7.6) - [CVE-2026-46680](https://insights.sbomify.com/CVE-2026-46680/): containerd user ID handling bypass allows runAsNonRoot evasion (high 7.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-64329 and fix it if it is affected. What it is: CVE-2025-64329 is a medium-severity denial of service vulnerability in containerd, published on 7 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-64329 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/containerd/containerd/v2 (Go): affected all versions; fixed in 2.0.7, 2.1.5, 2.2.0 - github.com/containerd/containerd/v2 (Go): affected all versions; fixed in 2.0.7 - github.com/containerd/containerd/v2 (Go): affected all versions; fixed in 2.0.7 - github.com/containerd/containerd/v2 (Go): affected from 2.1.0-beta.0; fixed in 2.1.5 - github.com/containerd/containerd/v2 (Go): affected from 2.1.0-beta.0; fixed in 2.1.5 - github.com/containerd/containerd/v2 (Go): affected from 2.2.0-beta.0; fixed in 2.2.0 - github.com/containerd/containerd/v2 (Go): affected from 2.2.0-beta.0; fixed in 2.2.0 - github.com/containerd/containerd (Go): affected all versions; fixed in 1.7.29 - github.com/containerd/containerd (Go): affected all versions; fixed in 1.7.29 - github.com/containerd/containerd (Go): affected all versions; fixed in 1.7.29 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-64329/ (Markdown: https://insights.sbomify.com/CVE-2025-64329/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64329 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64329 - OSV: https://osv.dev/vulnerability/CVE-2025-64329 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-64329/ Summaries are generated and may contain mistakes; the official description above is the record.