<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 23:00:03 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02731</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02731</link>
      <description>bdu:2026-02731</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02731</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-25621</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-25621</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: containerd, Alpaquita:25: containerd, Alpaquita:stream: containerd&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: containerd, Alpaquita:25: containerd, Alpaquita:stream: containerd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-25621</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1036 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1036</link>
      <description>certfr-2025-avi-1036</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1036</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-CD03295 — Security fixes in rancher-agent 2.11.15-r1</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-cd03295</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: rancher-agent&lt;/p&gt;
&lt;p&gt;Package rancher-agent version 2.11.15-r1 fixes 28 vulnerabilities: CVE-2026-53492, CVE-2026-50195, CVE-2026-53489, CVE-2024-40635, CVE-2024-25621...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: rancher-agent&lt;/p&gt;
&lt;p&gt;Package rancher-agent version 2.11.15-r1 fixes 28 vulnerabilities: CVE-2026-53492, CVE-2026-50195, CVE-2026-53489, CVE-2024-40635, CVE-2024-25621...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-cd03295</guid>
    </item>
    <item>
      <title>EUVD-2026-260238</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-260238</link>
      <description>EUVD-2026-260238</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-260238</guid>
    </item>
    <item>
      <title>fkie_cve-2024-25621</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-25621</link>
      <description>&lt;p&gt;containerd is an open-source container runtime. Versions 0.1.0 through 1.7.28, 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 have an overly broad default permission vulnerability. Directory paths `/var/lib/containerd`, `/run/containerd/io.containerd.grpc.v1.cri` and `/run/containerd/io.containerd.sandbox.controller.v1.shim` were all created with incorrect permissions. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. Workarounds include updating system administrator permissions so the host can manually chmod the directories to not have group or world accessible permissions, or to run containerd in rootless mode.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;containerd is an open-source container runtime. Versions 0.1.0 through 1.7.28, 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 have an overly broad default permission vulnerability. Directory paths `/var/lib/containerd`, `/run/containerd/io.containerd.grpc.v1.cri` and `/run/containerd/io.containerd.sandbox.controller.v1.shim` were all created with incorrect permissions. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. Workarounds include updating system administrator permissions so the host can manually chmod the directories to not have group or world accessible permissions, or to run containerd in rootless mode.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-25621</guid>
    </item>
    <item>
      <title>GHSA-pwhc-rpq9-4c8w — containerd affected by a local privilege escalation via wide permissions on CRI directory</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pwhc-rpq9-4c8w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containerd/containerd, Go: github.com/containerd/containerd/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An overly broad default permission vulnerability was found in containerd.&lt;/p&gt;
&lt;p&gt;- `/var/lib/containerd` was created with the permission bits 0o711, while it should be created with 0o700
  - Allowed local users on the host to potentially access the metadata store and the content store
- `/run/containerd/io.containerd.grpc.v1.cri` was created with 0o755, while it should be created with 0o700
  - Allowed local users on the host to potentially access the contents of Kubernetes local volumes. The contents of volumes might include setuid binaries, which could allow a local user on the host to elevate privileges on the host.
- `/run/containerd/io.containerd.sandbox.controller.v1.shim` was created with 0o711, while it should be created with 0o700&lt;/p&gt;
&lt;p&gt;The directory paths may differ depending on the daemon configuration.
When the `temp` directory path is specified in the daemon configuration, that directory was also created with 0o711, while it should be created with 0o700.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This bug has been fixed in the following containerd versions:&lt;/p&gt;
&lt;p&gt;* 2.2.0
* 2.1.5
* 2.0.7
* 1.7.29&lt;/p&gt;
&lt;p&gt;Users should update to these versions to resolve the issue.
These updates automatically change the permissions of the existing directories.&lt;/p&gt;
&lt;p&gt;&amp;gt; [!NOTE]
&amp;gt;
&amp;gt; `/run/containerd` and `/run/containerd/io.containerd.runtime.v2.task` are still created with 0o711.
&amp;gt; This is an expected behavior for supporting userns-remapped containers.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;The system administrator on the host can manually chmod th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containerd/containerd, Go: github.com/containerd/containerd/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An overly broad default permission vulnerability was found in containerd.&lt;/p&gt;
&lt;p&gt;- `/var/lib/containerd` was created with the permission bits 0o711, while it should be created with 0o700
  - Allowed local users on the host to potentially access the metadata store and the content store
- `/run/containerd/io.containerd.grpc.v1.cri` was created with 0o755, while it should be created with 0o700
  - Allowed local users on the host to potentially access the contents of Kubernetes local volumes. The contents of volumes might include setuid binaries, which could allow a local user on the host to elevate privileges on the host.
- `/run/containerd/io.containerd.sandbox.controller.v1.shim` was created with 0o711, while it should be created with 0o700&lt;/p&gt;
&lt;p&gt;The directory paths may differ depending on the daemon configuration.
When the `temp` directory path is specified in the daemon configuration, that directory was also created with 0o711, while it should be created with 0o700.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This bug has been fixed in the following containerd versions:&lt;/p&gt;
&lt;p&gt;* 2.2.0
* 2.1.5
* 2.0.7
* 1.7.29&lt;/p&gt;
&lt;p&gt;Users should update to these versions to resolve the issue.
These updates automatically change the permissions of the existing directories.&lt;/p&gt;
&lt;p&gt;&amp;gt; [!NOTE]
&amp;gt;
&amp;gt; `/run/containerd` and `/run/containerd/io.containerd.runtime.v2.task` are still created with 0o711.
&amp;gt; This is an expected behavior for supporting userns-remapped containers.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;The system administrator on the host can manually chmod th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pwhc-rpq9-4c8w</guid>
    </item>
    <item>
      <title>gsd-2024-25621</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-25621</link>
      <description>gsd-2024-25621</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-25621</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-25621 — containerd affected by a local privilege escalation via wide permissions on CRI directory</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-25621</link>
      <description>msrc_CVE-2024-25621</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-25621</guid>
    </item>
    <item>
      <title>OESA-2025-2752 — containerd security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2752</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: containerd&lt;/p&gt;
&lt;p&gt;containerd is an industry-standard container runtime with an emphasis on simplicity, robustness and portability.  It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;An overly broad default permission vulnerability was found in containerd.&lt;/p&gt;
&lt;p&gt;- `/var/lib/containerd` was created with the permission bits 0o711, while it should be created with 0o700
  - Allowed local users on the host to potentially access the metadata store and the content store
- `/run/containerd/io.containerd.grpc.v1.cri` was created with 0o755, while it should be created with 0o700
  - Allowed local users on the host to potentially access the contents of Kubernetes local volumes. The contents of volumes might include setuid binaries, which could allow a local user on the host to elevate privileges on the host.
- `/run/containerd/io.containerd.sandbox.controller.v1.shim` was created with 0o711, while it should be created with 0o700&lt;/p&gt;
&lt;p&gt;The directory paths may differ depending on the daemon configuration.
When the `temp` directory path is specified in the daemon configuration, that directory was also created with 0o711, while it should be created with 0o700.(CVE-2024-25621)&lt;/p&gt;
&lt;p&gt;A bug was found in containerd&amp;amp;apos;s CRI Attach implementation where a user can exhaust memory on the host due to goroutine leaks. Repetitive…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: containerd&lt;/p&gt;
&lt;p&gt;containerd is an industry-standard container runtime with an emphasis on simplicity, robustness and portability.  It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;An overly broad default permission vulnerability was found in containerd.&lt;/p&gt;
&lt;p&gt;- `/var/lib/containerd` was created with the permission bits 0o711, while it should be created with 0o700
  - Allowed local users on the host to potentially access the metadata store and the content store
- `/run/containerd/io.containerd.grpc.v1.cri` was created with 0o755, while it should be created with 0o700
  - Allowed local users on the host to potentially access the contents of Kubernetes local volumes. The contents of volumes might include setuid binaries, which could allow a local user on the host to elevate privileges on the host.
- `/run/containerd/io.containerd.sandbox.controller.v1.shim` was created with 0o711, while it should be created with 0o700&lt;/p&gt;
&lt;p&gt;The directory paths may differ depending on the daemon configuration.
When the `temp` directory path is specified in the daemon configuration, that directory was also created with 0o711, while it should be created with 0o700.(CVE-2024-25621)&lt;/p&gt;
&lt;p&gt;A bug was found in containerd&amp;amp;apos;s CRI Attach implementation where a user can exhaust memory on the host due to goroutine leaks. Repetitive…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2752</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:15726-1 — containerd-1.7.29-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:15726-1</link>
      <description>&lt;p&gt;containerd-1.7.29-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;containerd-1.7.29-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:15726-1</guid>
    </item>
    <item>
      <title>RHSA-2025:22955 — Red Hat Security Advisory: Red Hat OpenStack Platform 17.1.12 director Operator container images</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:22955</link>
      <description>&lt;p&gt;github.com/containerd/containerd: containerd local privilege escalation golang.org/x/crypto/ssh/agent: golang.org/x/crypto/ssh/agent: SSH client panic due to unexpected SSH_AGENT_SUCCESS&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;github.com/containerd/containerd: containerd local privilege escalation golang.org/x/crypto/ssh/agent: golang.org/x/crypto/ssh/agent: SSH client panic due to unexpected SSH_AGENT_SUCCESS&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:22955</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:21042-1 — Security update for containerd</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:21042-1</link>
      <description>&lt;p&gt;Security update for containerd&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for containerd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:21042-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-25621</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-25621</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: containerd, Ubuntu:Pro:18.04:LTS: containerd, Ubuntu:Pro:20.04:LTS: containerd, Ubuntu:Pro:20.04:LTS: containerd-app, Ubuntu:22.04:LTS: containerd, Ubuntu:Pro:22.04:LTS: containerd-app, Ubuntu:24.04:LTS: containerd-app, Ubuntu:Pro:24.04:LTS: containerd, Ubuntu:25.10: containerd, Ubuntu:25.10: containerd-app&lt;/p&gt;
&lt;p&gt;containerd is an open-source container runtime. Versions 0.1.0 through 1.7.28, 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 have an overly broad default permission vulnerability. Directory paths `/var/lib/containerd`, `/run/containerd/io.containerd.grpc.v1.cri` and `/run/containerd/io.containerd.sandbox.controller.v1.shim` were all created with incorrect permissions. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. Workarounds include updating system administrator permissions so the host can manually chmod the directories to not have group or world accessible permissions, or to run containerd in rootless mode.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: containerd, Ubuntu:Pro:18.04:LTS: containerd, Ubuntu:Pro:20.04:LTS: containerd, Ubuntu:Pro:20.04:LTS: containerd-app, Ubuntu:22.04:LTS: containerd, Ubuntu:Pro:22.04:LTS: containerd-app, Ubuntu:24.04:LTS: containerd-app, Ubuntu:Pro:24.04:LTS: containerd, Ubuntu:25.10: containerd, Ubuntu:25.10: containerd-app&lt;/p&gt;
&lt;p&gt;containerd is an open-source container runtime. Versions 0.1.0 through 1.7.28, 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 have an overly broad default permission vulnerability. Directory paths `/var/lib/containerd`, `/run/containerd/io.containerd.grpc.v1.cri` and `/run/containerd/io.containerd.sandbox.controller.v1.shim` were all created with incorrect permissions. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. Workarounds include updating system administrator permissions so the host can manually chmod the directories to not have group or world accessible permissions, or to run containerd in rootless mode.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-25621</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2563 — Microsoft Azure Linux: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2563</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Microsoft Azure Linux und Microsoft Windows ausnutzen um erhöhte Privilegien zu erlangen, beliebigen Code auszuführen, die Authentifizierung zu umgehen,  Spoofing-Angriffe durchzuführen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Microsoft Azure Linux und Microsoft Windows ausnutzen um erhöhte Privilegien zu erlangen, beliebigen Code auszuführen, die Authentifizierung zu umgehen,  Spoofing-Angriffe durchzuführen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2563</guid>
    </item>
  </channel>
</rss>
