<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T14:13:17.120282+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/alsa-2021:2291</id>
    <title>ALSA-2021:2291 — Important: container-tools:2.0 security update</title>
    <updated>2026-10-02T14:13:17.164966+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:8: cockpit-podman, AlmaLinux:8: conmon, AlmaLinux:8: container-selinux, AlmaLinux:8: containernetworking-plugins, AlmaLinux:8: containers-common, AlmaLinux:8: crit, AlmaLinux:8: criu, AlmaLinux:8: fuse-overlayfs, AlmaLinux:8: python-podman-api, AlmaLinux:8: python3-criu and 5 more</p>
<p>The container-tools module contains tools for working with containers, notably podman, buildah, skopeo, and runc.</p>
<p>Security Fix(es):</p>
<p>* runc: vulnerable to symlink exchange attack (CVE-2021-30465)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/alsa-2021:2291"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2021-03670</id>
    <title>bdu:2021-03670</title>
    <updated>2026-10-02T14:13:17.165067+00:00</updated>
    <content>bdu:2021-03670</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2021-03670"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2021-30465</id>
    <title>Withdrawn: BELL-CVE-2021-30465 — CVE-2021-30465 does not affect BellSoft software</title>
    <updated>2026-10-02T14:13:17.165085+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <strong>Withdrawn by the publisher.</strong>
        </p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2021-30465"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2022-avi-591</id>
    <title>certfr-2022-avi-591 — De multiples vulnérabilités ont été découvertes dans les produits IBM.
Certaines d'entre elles permettent à un attaquan…</title>
    <updated>2026-10-02T14:13:17.165101+00:00</updated>
    <content>certfr-2022-avi-591</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2022-avi-591"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-cn11164</id>
    <title>Withdrawn: CLEANSTART-2026-CN11164 — Security fixes in runc 1.0.0_rc95-r0</title>
    <updated>2026-10-02T14:13:17.165116+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> CleanStart: runc</p>
<p>Package runc version 1.0.0_rc95-r0 fixes 1 vulnerabilities: CVE-2021-30465</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-cn11164"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-26802</id>
    <title>EUVD-2026-26802</title>
    <updated>2026-10-02T14:13:17.165136+00:00</updated>
    <content>EUVD-2026-26802</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-26802"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-30465</id>
    <title>fkie_cve-2021-30465</title>
    <updated>2026-10-02T14:13:17.165147+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the vulnerability, an attacker must be able to create multiple containers with a fairly specific mount configuration. The problem occurs via a symlink-exchange attack that relies on a race condition.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-30465"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-c3xm-pvg7-gh7r</id>
    <title>GHSA-c3xm-pvg7-gh7r — mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs</title>
    <updated>2026-10-02T14:13:17.165167+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/opencontainers/runc</p>
<p>### Summary</p>
<p>runc 1.0.0-rc94 and earlier are vulnerable to a symlink exchange attack whereby
an attacker can request a seemingly-innocuous container configuration that
actually results in the host filesystem being bind-mounted into the container
(allowing for a container escape). CVE-2021-30465 has been assigned for this
issue.</p>
<p>An attacker must have the ability to start containers using some kind of custom
volume configuration, and while recommended container hardening mechanisms such
as LSMs (AppArmor/SELinux) and user namespaces will restrict the amount of
damage an attacker could do, they do not block this attack outright. We have a
reproducer using Kubernetes (and the below description mentions
Kubernetes-specific paths), but this is not a Kubernetes-specific issue.</p>
<p>The now-released [runc v1.0.0-rc95][release] contains a fix for this issue, we
recommend users update as soon as possible.</p>
<p>[release]: https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc95</p>
<p>### Details</p>
<p>In circumstances where a container is being started, and runc is mounting
inside a volume shared with another container (which is conducting a
symlink-exchange attack), runc can be tricked into mounting outside of the
container rootfs by swapping the target of a mount with a symlink due to a
time-of-check-to-time-of-use (TOCTTOU) flaw. This is fairly similar in style to
previous TOCTTOU attacks (and is a problem we are working on solving with
libpathrs).</p>
<p>However, this alone is not useful because t…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-c3xm-pvg7-gh7r"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-30465</id>
    <title>gsd-2021-30465</title>
    <updated>2026-10-02T14:13:17.165215+00:00</updated>
    <content>gsd-2021-30465</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-30465"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2021-1215</id>
    <title>OESA-2021-1215 — runc security update</title>
    <updated>2026-10-02T14:13:17.165227+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: runc</p>
<p>runc is a CLI tool for spawning and running containers according to the OCI specification.

Security Fix(es):

runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the vulnerability, an attacker must be able to create multiple containers with a fairly specific mount configuration. The problem occurs via a symlink-exchange attack that relies on a race condition.(CVE-2021-30465)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2021-1215"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2021:1404-1</id>
    <title>openSUSE-SU-2021:1404-1 — Security update for containerd, docker, runc</title>
    <updated>2026-10-02T14:13:17.165246+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for containerd, docker, runc</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2021:1404-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2021:1562</id>
    <title>RHSA-2021:1562 — Red Hat Security Advisory: OpenShift Container Platform 4.7.12 packages and security update</title>
    <updated>2026-10-02T14:13:17.165272+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>golang: crypto/elliptic: incorrect operations on the P-224 curve runc: vulnerable to symlink exchange attack</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2021:1562"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2021:3336-1</id>
    <title>SUSE-SU-2021:3336-1 — Security update for containerd, docker, runc</title>
    <updated>2026-10-02T14:13:17.165291+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for containerd, docker, runc</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2021:3336-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-30465</id>
    <title>UBUNTU-CVE-2021-30465</title>
    <updated>2026-10-02T14:13:17.165306+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: runc, Ubuntu:18.04:LTS: runc, Ubuntu:20.04:LTS: runc</p>
<p>runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the vulnerability, an attacker must be able to create multiple containers with a fairly specific mount configuration. The problem occurs via a symlink-exchange attack that relies on a race condition.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-30465"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0510</id>
    <title>WID-SEC-W-2022-0510 — IBM DB2: Mehrere Schwachstellen</title>
    <updated>2026-10-02T14:13:17.165327+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM DB2 ausnutzen, um Dateien zu manipulieren, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, willkürlichen Code mit erhöhten Rechten auszuführen, Informationen falsch darzustellen und beliebigen Code auszuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0510"/>
  </entry>
</feed>
