{"answers":{"affected":"3 open source packages ship an affected version, including github.com/containerd/containerd/v2. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-47291 in the wild and no public exploit code.","fix":"Upgrade github.com/containerd/containerd/v2 to 2.0.5 or later.","what":"CVE-2025-47291 is a medium-severity vulnerability in containerd, published on 21 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47291 and fix it if it is affected.\n\nWhat it is: CVE-2025-47291 is a medium-severity vulnerability in containerd, published on 21 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-47291 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/containerd/containerd/v2 (Go): affected from 2.0.1; fixed in 2.0.5\n- github.com/containerd/containerd/v2 (Go): affected from 2.0.1; fixed in 2.0.5\n- github.com/containerd/containerd/v2 (Go): affected from 2.0.1; fixed in 2.0.5\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-47291/ (Markdown: https://insights.sbomify.com/CVE-2025-47291/index.md)","id":"CVE-2025-47291","markdown":"https://insights.sbomify.com/CVE-2025-47291/index.md","name":"CVE-2025-47291","record":{"aliases":["AZL-62003","GHSA-cxfp-7pvr-95ff","GO-2025-3701","MINI-mr8c-4jmc-7x8w","UBUNTU-CVE-2025-47291"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"container runtime","requires_auth":"none","summary":"Attackers can cause denial of service on Kubernetes nodes by exploiting incorrect cgroup assignments in usernamespaced containers.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"containerd","vendor":"linuxfoundation"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"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/E:U","version":"4.0"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"containerd is an open-source container runtime. A bug was found in the containerd's CRI implementation where containerd, starting in version 2.0.1 and prior to version 2.0.5, doesn't put usernamespaced containers under the Kubernetes' cgroup hierarchy, therefore some Kubernetes limits are not honored. This may cause a denial of service of the Kubernetes node. This bug has been fixed in containerd 2.0.5+ and 2.1.0+. Users should update to these versions to resolve the issue. As a workaround, disable usernamespaced pods in Kubernetes temporarily.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"containerd CRI plugin: Incorrect cgroup hierarchy assignment for containers running in usernamespaced Kubernetes pods.","id":"CVE-2025-47291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"Cap Collectif vulnerable to insecure deserialization leading to remote code execution","id":"CVE-2025-47292"},"packages":[{"ecosystem":"Go","fixed":["2.0.5"],"introduced":["2.0.1"],"last_affected":[],"package":"github.com/containerd/containerd/v2","purl":null,"source":"GHSA-cxfp-7pvr-95ff"},{"ecosystem":"Go","fixed":["2.0.5"],"introduced":["2.0.1"],"last_affected":[],"package":"github.com/containerd/containerd/v2","purl":"pkg:golang/github.com/containerd/containerd/v2","source":"GHSA-cxfp-7pvr-95ff"},{"ecosystem":"Go","fixed":["2.0.5"],"introduced":["2.0.1"],"last_affected":[],"package":"github.com/containerd/containerd/v2","purl":"pkg:golang/github.com/containerd/containerd/v2","source":"GO-2025-3701"}],"prev":{"headline":"Containerd vulnerable to host filesystem access during image unpack","id":"CVE-2025-47290"},"products":["containerd"],"published":"2025-05-21","related":[{"cvss_score":9.4,"headline":"containerd CRI — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull","id":"CVE-2026-53488","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":8.4,"headline":"containerd CRI checkpoint restore CDI annotation smuggling","id":"CVE-2026-53492","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":8.2,"headline":"containerd: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore","id":"CVE-2026-53489","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":7.6,"headline":"Containerd vulnerable to host filesystem access during image unpack","id":"CVE-2025-47290","kev_date_added":null,"published":"2025-05-20"},{"cvss_score":7.3,"headline":"containerd user ID handling bypass allows runAsNonRoot evasion","id":"CVE-2026-46680","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":7.3,"headline":"containerd affected by a local privilege escalation via wide permissions on CRI directory","id":"CVE-2024-25621","kev_date_added":null,"published":"2025-11-06"},{"cvss_score":6.9,"headline":"containerd CRI server: Host memory exhaustion through Attach goroutine leak","id":"CVE-2025-64329","kev_date_added":null,"published":"2025-11-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-21","vendors":["containerd"]},"summary":"Attackers can cause denial of service on Kubernetes nodes by exploiting incorrect cgroup assignments in usernamespaced containers.","url":"https://insights.sbomify.com/CVE-2025-47291/"}