ChangeIntel IT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord
CVE-2025-64329

containerd CRI server: Host memory exhaustion through Attach goroutine leak

CVSS 4.0 6.9 MEDIUMEUVD CVSS 4.0 6.9 CVSS 4.0 · [email protected] · Secondary 6.9 MEDIUMCVSS 3.1 · [email protected] · Primary 5.5 MEDIUMCVSS_V4 Publisher rating MODERATEFixed by github.com/containerd/containerd 1.7.29Fixed by github.com/containerd/containerd/v2 2.0.7Fixed by github.com/containerd/containerd/v2 2.1.5Fixed by github.com/containerd/containerd/v2 2.2.0osv · severity unknownFixed by github.com/containerd/containerd 1.7.29Fixed by github.com/containerd/containerd/v2 2.0.7Fixed by github.com/containerd/containerd/v2 2.1.5Fixed by github.com/containerd/containerd/v2 2.2.0KEV status unknown
Original advisory

cve-program · CVE-2025-64329

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-38219

Published

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.

Read the publisher's advisory

nvd · CVE-2025-64329

Published

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.

Read the publisher's advisory

osv · GHSA-m6hq-p25p-ffr2

Published

### 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)

Read the publisher's advisory

osv · GO-2025-4108

Published

containerd CRI server: Host memory exhaustion through Attach goroutine leak in github.com/containerd/containerd

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-64329

Published

containerd

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "containerd",
                    "product": "containerd",
                    "versions": [
                        {
                            "version": "< 1.7.29",
                            "status": "affected"
                        },
                        {
                            "version": "< 2.0.7",
                            "status": "affected"
                        },
                        {
                            "version": ">= 2.1.0-beta.0, < 2.1.5",
                            "status": "affected"
                        },
                        {
                            "version": ">= 2.2.0-beta.0, < 2.2.0",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-38219

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 7, 2025, 4:15:09 AM

dateUpdated: Nov 7, 2025, 5:42:07 PM

11 related source bulletins · separate from aliases

openSUSE-SU-2025:15726-1: containerd-1.7.29-1.1 on GA media

CVE-2024-25621 · CVE-2025-64329

SUSE-SU-2025:21042-1: Security update for containerd

CVE-2024-25621 · CVE-2025-64329

SUSE-SU-2025:4288-1: Security update for containerd

CVE-2024-25621 · CVE-2025-64329

RHSA-2026:37387: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update

CVE-2024-25621 · CVE-2024-40635 · CVE-2024-45310 · CVE-2025-8766 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22870 · CVE-2025-47911 · CVE-2025-52881 · CVE-2025-54410 · CVE-2025-58058 · CVE-2025-64329 · CVE-2025-66506 · CVE-2026-22772 · CVE-2026-23831 · CVE-2026-24117 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-25934 · CVE-2026-27136 · CVE-2026-27141 · CVE-2026-27903 · CVE-2026-33540 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-35172 · CVE-2026-35469 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-39883 · CVE-2026-41506 · CVE-2026-41567 · CVE-2026-41568 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-45571 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598

WID-SEC-W-2026-0778: Dell Secure Connect Gateway Policy Manager: Mehrere Schwachstellen

CVE-2014-8991 · CVE-2015-2296 · CVE-2019-6778 · CVE-2020-10756 · CVE-2020-13645 · CVE-2020-1983 · CVE-2020-24455 · CVE-2020-25219 · CVE-2020-26154 · CVE-2020-29130 · CVE-2021-3592 · CVE-2021-3593 · CVE-2021-3594 · CVE-2021-3595 · CVE-2022-40897 · CVE-2023-22745 · CVE-2023-5752 · CVE-2024-25621 · CVE-2024-29040 · CVE-2024-6345 · CVE-2025-10911 · CVE-2025-11226 · CVE-2025-11468 · CVE-2025-11563 · CVE-2025-11731 · CVE-2025-12084 · CVE-2025-12781 · CVE-2025-1352 · CVE-2025-13601 · CVE-2025-1372 · CVE-2025-1376 · CVE-2025-1377 · CVE-2025-13836 · CVE-2025-13837 · CVE-2025-14087 · CVE-2025-14512 · CVE-2025-15281 · CVE-2025-15282 · CVE-2025-15366 · CVE-2025-15367 · CVE-2025-15467 · CVE-2025-24294 · CVE-2025-28162 · CVE-2025-28164 · CVE-2025-31133 · CVE-2025-3576 · CVE-2025-47273 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-53057 · CVE-2025-53666 · CVE-2025-54770 · CVE-2025-54771 · CVE-2025-54798 · CVE-2025-55752 · CVE-2025-59375 · CVE-2025-6075 · CVE-2025-61661 · CVE-2025-61662 · CVE-2025-61663 · CVE-2025-61664 · CVE-2025-61748 · CVE-2025-61795 · CVE-2025-61984 · CVE-2025-61985 · CVE-2025-64329 · CVE-2025-64505 · CVE-2025-64506 · CVE-2025-64720 · CVE-2025-64756 · CVE-2025-65018 · CVE-2025-66035 · CVE-2025-66293 · CVE-2025-66412 · CVE-2025-66614 · CVE-2025-67721 · CVE-2025-68160 · CVE-2025-68973 · CVE-2025-69418 · CVE-2025-69419 · CVE-2025-69420 · CVE-2025-69421 · CVE-2025-69873 · CVE-2025-7039 · CVE-2025-8291 · CVE-2025-9187 · CVE-2025-9820 · CVE-2026-0672 · CVE-2026-0861 · CVE-2026-0865 · CVE-2026-0915 · CVE-2026-0988 · CVE-2026-1484 · CVE-2026-1485 · CVE-2026-1489 · CVE-2026-22610 · CVE-2026-22695 · CVE-2026-22795 · CVE-2026-22796 · CVE-2026-22801 · CVE-2026-24734 · CVE-2026-24882 · CVE-2026-25646

WID-SEC-W-2025-2563: Microsoft Azure Linux: Mehrere Schwachstellen

CVE-2024-25621 · CVE-2025-10966 · CVE-2025-12863 · CVE-2025-12875 · CVE-2025-31133 · CVE-2025-40107 · CVE-2025-40109 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-60753 · CVE-2025-62220 · CVE-2025-64329 · CVE-2025-64432 · CVE-2025-64433 · CVE-2025-64434 · CVE-2025-64435 · CVE-2025-64436 · CVE-2025-64437

SUSE-SU-2025:4072-1: Security update for containerd

CVE-2024-25621 · CVE-2025-64329

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

CVE-2025-64329

openSUSE-SU-2026:21213-1: Security update for containerd

CVE-2024-25621 · CVE-2025-64329 · CVE-2026-33186 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-35469 · CVE-2026-39821 · CVE-2026-46680 · CVE-2026-47262 · CVE-2026-53488

RHSA-2026:2900: Red Hat Security Advisory: Network Observability 1.11.0 for OpenShift

CVE-2024-25621 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-64329 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-23745 · CVE-2026-24049 · CVE-2026-24842

SUSE-SU-2025:21057-1: Security update for containerd

CVE-2024-25621 · CVE-2025-64329

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-64329

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-401

Original publisher date fields

published: 2025-11-07T05:16:08.017

lastModified: 2026-06-17T09:54:13.263

6 source CPE criteria · context only
  • cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:2.2.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:2.2.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:2.2.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:2.2.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:containerd:2.2.0:rc1:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-m6hq-p25p-ffr2

Published

github.com/containerd/containerd

Go

SEMVER · introduced 0 → fixed 1.7.29

github.com/containerd/containerd/v2

Go

SEMVER · introduced 0 → fixed 2.0.7

github.com/containerd/containerd/v2

Go

SEMVER · introduced 2.1.0-beta.0 → fixed 2.1.5

github.com/containerd/containerd/v2

Go

SEMVER · introduced 2.2.0-beta.0 → fixed 2.2.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2025-4108

Published

github.com/containerd/containerd

Go

SEMVER · introduced 0 → fixed 1.7.29

github.com/containerd/containerd/v2

Go

SEMVER · introduced 0 → fixed 2.0.7 → introduced 2.1.0-beta.0 → fixed 2.1.5 → introduced 2.2.0-beta.0 → fixed 2.2.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 20:10 UTC · 254 of 275 readable · 250 fully read · documentation 468/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners.