<?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 10:56:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2022-05412</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2022-05412</link>
      <description>bdu:2022-05412</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2022-05412</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2022-31030 — CVE-2022-31030 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2022-31030</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2022-31030</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0199 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;les produits IBM&lt;/span&gt;. Certaines d'entre el…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0199</link>
      <description>certfr-2024-avi-0199</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0199</guid>
    </item>
    <item>
      <title>CLEANSTART-2025-UG08794 — containerd is an open source container runtime</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2025-ug08794</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: containerd&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the containerd package. containerd is an open source container runtime.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: containerd&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the containerd package. containerd is an open source container runtime.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2025-ug08794</guid>
    </item>
    <item>
      <title>EUVD-2026-16785</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-16785</link>
      <description>EUVD-2026-16785</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-16785</guid>
    </item>
    <item>
      <title>fkie_cve-2022-31030</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31030</link>
      <description>&lt;p&gt;containerd is an open source container runtime. A bug was found in the containerd&amp;#39;s CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd&amp;#39;s CRI implementation; `ExecSync` may be used when running probes or when executing processes via an &amp;#34;exec&amp;#34; facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;containerd is an open source container runtime. A bug was found in the containerd&amp;#39;s CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd&amp;#39;s CRI implementation; `ExecSync` may be used when running probes or when executing processes via an &amp;#34;exec&amp;#34; facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-31030</guid>
    </item>
    <item>
      <title>GHSA-5ffw-gxpp-mxpf — containerd CRI plugin: Host memory exhaustion through ExecSync</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5ffw-gxpp-mxpf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containerd/containerd&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A bug was found in containerd&amp;#39;s CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API.  This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads.  Kubernetes and crictl can both be configured to use containerd&amp;#39;s CRI implementation; `ExecSync` may be used when running probes or when executing processes via an &amp;#34;exec&amp;#34; facility.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This bug has been fixed in containerd 1.6.6 and 1.5.13.  Users should update to these versions to resolve the issue.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Ensure that only trusted images and commands are used.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* Similar fix in cri-o&amp;#39;s CRI implementation https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;The containerd project would like to thank David Korczynski and Adam Korczynski of ADA Logics for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md) during a security audit sponsored by CNCF and facilitated by OSTIF.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containerd/containerd&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A bug was found in containerd&amp;#39;s CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API.  This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads.  Kubernetes and crictl can both be configured to use containerd&amp;#39;s CRI implementation; `ExecSync` may be used when running probes or when executing processes via an &amp;#34;exec&amp;#34; facility.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This bug has been fixed in containerd 1.6.6 and 1.5.13.  Users should update to these versions to resolve the issue.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Ensure that only trusted images and commands are used.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* Similar fix in cri-o&amp;#39;s CRI implementation https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;The containerd project would like to thank David Korczynski and Adam Korczynski of ADA Logics for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md) during a security audit sponsored by CNCF and facilitated by OSTIF.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5ffw-gxpp-mxpf</guid>
    </item>
    <item>
      <title>gsd-2022-31030</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-31030</link>
      <description>gsd-2022-31030</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-31030</guid>
    </item>
    <item>
      <title>msrc_CVE-2022-31030 — containerd CRI plugin: Host memory exhaustion through ExecSync</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2022-31030</link>
      <description>msrc_CVE-2022-31030</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2022-31030</guid>
    </item>
    <item>
      <title>OESA-2022-1743 — containerd security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2022-1743</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: containerd, openEuler:20.03-LTS-SP3: containerd, openEuler:22.03-LTS: 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):&#13;
&#13;
containerd is an open source container runtime. A bug was found in the containerd&amp;amp;apos;s CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd&amp;amp;apos;s CRI implementation; `ExecSync` may be used when running probes or when executing processes via an &amp;amp;quot;exec&amp;amp;quot; facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.(CVE-2022-31030)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: containerd, openEuler:20.03-LTS-SP3: containerd, openEuler:22.03-LTS: 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):&#13;
&#13;
containerd is an open source container runtime. A bug was found in the containerd&amp;amp;apos;s CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd&amp;amp;apos;s CRI implementation; `ExecSync` may be used when running probes or when executing processes via an &amp;amp;quot;exec&amp;amp;quot; facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.(CVE-2022-31030)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2022-1743</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:12130-1 — containerd-1.6.6-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:12130-1</link>
      <description>&lt;p&gt;containerd-1.6.6-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;containerd-1.6.6-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:12130-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2022:2165-1 — Security update for containerd</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2022:2165-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-2022:2165-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-31030</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31030</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: containerd, Ubuntu:18.04:LTS: containerd, Ubuntu:20.04:LTS: containerd, Ubuntu:22.04:LTS: containerd&lt;/p&gt;
&lt;p&gt;containerd is an open source container runtime. A bug was found in the containerd&amp;#39;s CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd&amp;#39;s CRI implementation; `ExecSync` may be used when running probes or when executing processes via an &amp;#34;exec&amp;#34; facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: containerd, Ubuntu:18.04:LTS: containerd, Ubuntu:20.04:LTS: containerd, Ubuntu:22.04:LTS: containerd&lt;/p&gt;
&lt;p&gt;containerd is an open source container runtime. A bug was found in the containerd&amp;#39;s CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd&amp;#39;s CRI implementation; `ExecSync` may be used when running probes or when executing processes via an &amp;#34;exec&amp;#34; facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31030</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-3146 — IBM MQ Operator and Queue manager: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-3146</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in IBM MQ Operator and Queue manager ausnutzen, um einen Denial of Service Angriff durchzuführen, Informationen offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in IBM MQ Operator and Queue manager ausnutzen, um einen Denial of Service Angriff durchzuführen, Informationen offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-3146</guid>
    </item>
  </channel>
</rss>
