https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 04:29:35 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0969 certfr-2025-avi-0969 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0969 https://cve.radiocsirt.org/vuln/euvd-2026-240751 EUVD-2026-240751 https://cve.radiocsirt.org/vuln/euvd-2026-240751 https://cve.radiocsirt.org/vuln/fkie_cve-2025-47291 <p>containerd is an open-source container runtime. A bug was found in the containerd&#39;s CRI implementation where containerd, starting in version 2.0.1 and prior to version 2.0.5, doesn&#39;t put usernamespaced containers under the Kubernetes&#39; 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.</p> <p>containerd is an open-source container runtime. A bug was found in the containerd&#39;s CRI implementation where containerd, starting in version 2.0.1 and prior to version 2.0.5, doesn&#39;t put usernamespaced containers under the Kubernetes&#39; 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-47291 https://cve.radiocsirt.org/vuln/ghsa-cxfp-7pvr-95ff <p><strong>Affected:</strong> Go: github.com/containerd/containerd/v2</p> <p># Impact</p> <p>A bug was found in the containerd&#39;s CRI implementation where containerd doesn&#39;t put usernamespaced containers under the Kubernetes&#39; cgroup hierarchy, therefore some Kubernetes limits are not honored. This may cause a denial of service of the Kubernetes node.</p> <p># Patches</p> <p>This bug has been fixed in containerd 2.0.5+ and 2.1.0+. Users should update to these versions to resolve the issue.</p> <p># Workarounds</p> <p>Disable usernamespaced pods in Kubernetes temporarily.</p> <p># Credits</p> <p>The containerd project would like to thank Rodrigo Campos Catelin and Piotr Rogowski for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md).</p> <p># For more information If you have any questions or comments about this advisory:</p> <p>* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose) * Email us at security@containerd.io</p> <p>To report a security issue in containerd: * [Report a new vulnerability](https://github.com/containerd/containerd/security/advisories/new) * Email us at [security@containerd.io](mailto:security@containerd.io)</p> <p><strong>Affected:</strong> Go: github.com/containerd/containerd/v2</p> <p># Impact</p> <p>A bug was found in the containerd&#39;s CRI implementation where containerd doesn&#39;t put usernamespaced containers under the Kubernetes&#39; cgroup hierarchy, therefore some Kubernetes limits are not honored. This may cause a denial of service of the Kubernetes node.</p> <p># Patches</p> <p>This bug has been fixed in containerd 2.0.5+ and 2.1.0+. Users should update to these versions to resolve the issue.</p> <p># Workarounds</p> <p>Disable usernamespaced pods in Kubernetes temporarily.</p> <p># Credits</p> <p>The containerd project would like to thank Rodrigo Campos Catelin and Piotr Rogowski for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md).</p> <p># For more information If you have any questions or comments about this advisory:</p> <p>* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose) * Email us at security@containerd.io</p> <p>To report a security issue in containerd: * [Report a new vulnerability](https://github.com/containerd/containerd/security/advisories/new) * Email us at [security@containerd.io](mailto:security@containerd.io)</p> https://cve.radiocsirt.org/vuln/ghsa-cxfp-7pvr-95ff https://cve.radiocsirt.org/vuln/msrc_cve-2025-47291 msrc_CVE-2025-47291 https://cve.radiocsirt.org/vuln/msrc_cve-2025-47291 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15159-1 <p>govulncheck-vulndb-0.0.20250523T151856-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20250523T151856-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15159-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-47291 <p><strong>Affected:</strong> Ubuntu:25.10: containerd-app</p> <p>containerd is an open-source container runtime. A bug was found in the containerd&#39;s CRI implementation where containerd, starting in version 2.0.1 and prior to version 2.0.5, doesn&#39;t put usernamespaced containers under the Kubernetes&#39; 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.</p> <p><strong>Affected:</strong> Ubuntu:25.10: containerd-app</p> <p>containerd is an open-source container runtime. A bug was found in the containerd&#39;s CRI implementation where containerd, starting in version 2.0.1 and prior to version 2.0.5, doesn&#39;t put usernamespaced containers under the Kubernetes&#39; 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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-47291