<?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 19:15:00 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-00284</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-00284</link>
      <description>bdu:2023-00284</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-00284</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2021-21334 — CVE-2021-21334 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2021-21334</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-2021-21334</guid>
    </item>
    <item>
      <title>certfr-2022-avi-624 — De multiples vulnérabilités ont été découvertes dans IBM MQ Operator et
Queue manager. Elles permettent à un attaquant…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2022-avi-624</link>
      <description>certfr-2022-avi-624</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2022-avi-624</guid>
    </item>
    <item>
      <title>CLEANSTART-2025-BS91981 — In containerd (an industry-standard container runtime) before versions 1</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2025-bs91981</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. In containerd (an industry-standard container runtime) before versions 1.&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. In containerd (an industry-standard container runtime) before versions 1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2025-bs91981</guid>
    </item>
    <item>
      <title>EUVD-2026-22126</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-22126</link>
      <description>EUVD-2026-22126</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-22126</guid>
    </item>
    <item>
      <title>fkie_cve-2021-21334</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-21334</link>
      <description>&lt;p&gt;In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd&amp;#39;s CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd&amp;#39;s CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd&amp;#39;s CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd&amp;#39;s CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-21334</guid>
    </item>
    <item>
      <title>GHSA-6g2q-w5j3-fwh4 — containerd environment variable leak</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6g2q-w5j3-fwh4</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;Containers launched through containerd&amp;#39;s CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers.  If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared.&lt;/p&gt;
&lt;p&gt;If you are not using containerd’s CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue.&lt;/p&gt;
&lt;p&gt;If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue.&lt;/p&gt;
&lt;p&gt;If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4.  Users should update to these versions as soon as they are released.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;There are no known workarounds.&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](https://github.com/containerd/containerd/issues/new/choose)
* Email us at security@containerd.io if you think you’ve found a security bug.&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;Containers launched through containerd&amp;#39;s CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers.  If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared.&lt;/p&gt;
&lt;p&gt;If you are not using containerd’s CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue.&lt;/p&gt;
&lt;p&gt;If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue.&lt;/p&gt;
&lt;p&gt;If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4.  Users should update to these versions as soon as they are released.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;There are no known workarounds.&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](https://github.com/containerd/containerd/issues/new/choose)
* Email us at security@containerd.io if you think you’ve found a security bug.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6g2q-w5j3-fwh4</guid>
    </item>
    <item>
      <title>gsd-2021-21334</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-21334</link>
      <description>gsd-2021-21334</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-21334</guid>
    </item>
    <item>
      <title>msrc_CVE-2021-21334 — environment variable leak</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2021-21334</link>
      <description>msrc_CVE-2021-21334</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2021-21334</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:10693-1 — containerd-1.4.8-2.2 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:10693-1</link>
      <description>&lt;p&gt;containerd-1.4.8-2.2 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;containerd-1.4.8-2.2 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:10693-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-21334</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-21334</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&lt;/p&gt;
&lt;p&gt;In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd&amp;#39;s CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd&amp;#39;s CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.&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&lt;/p&gt;
&lt;p&gt;In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd&amp;#39;s CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd&amp;#39;s CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-21334</guid>
    </item>
    <item>
      <title>WID-SEC-W-2022-1002 — Amazon Linux 2: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1002</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Amazon Linux 2 ausnutzen, um Informationen offenzulegen, Dateien zu manipulieren oder falsche Informationen darzustellen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Amazon Linux 2 ausnutzen, um Informationen offenzulegen, Dateien zu manipulieren oder falsche Informationen darzustellen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1002</guid>
    </item>
  </channel>
</rss>
