<?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>Fri, 02 Oct 2026 18:41:46 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:0922 — Important: podman security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:0922</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: podman, AlmaLinux:9: podman-docker, AlmaLinux:9: podman-plugins, AlmaLinux:9: podman-remote, AlmaLinux:9: podman-tests&lt;/p&gt;
&lt;p&gt;The podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* podman: buildah: Container breakout by using --jobs=2 and a race condition when building a malicious Containerfile (CVE-2024-11218)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: podman, AlmaLinux:9: podman-docker, AlmaLinux:9: podman-plugins, AlmaLinux:9: podman-remote, AlmaLinux:9: podman-tests&lt;/p&gt;
&lt;p&gt;The podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* podman: buildah: Container breakout by using --jobs=2 and a race condition when building a malicious Containerfile (CVE-2024-11218)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:0922</guid>
    </item>
    <item>
      <title>bdu:2025-01013</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01013</link>
      <description>bdu:2025-01013</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01013</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-11218</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-11218</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: buildah, Alpaquita:23: podman, Alpaquita:stream: buildah, Alpaquita:stream: podman&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: buildah, Alpaquita:23: podman, Alpaquita:stream: buildah, Alpaquita:stream: podman&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-11218</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0370 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0370</link>
      <description>certfr-2025-avi-0370</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0370</guid>
    </item>
    <item>
      <title>EUVD-2026-361948</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361948</link>
      <description>EUVD-2026-361948</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361948</guid>
    </item>
    <item>
      <title>fkie_cve-2024-11218</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-11218</link>
      <description>&lt;p&gt;A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-11218</guid>
    </item>
    <item>
      <title>GHSA-5vpc-35f4-r8w6 — Buildah allows build breakout using malicious Containerfiles and concurrent builds</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5vpc-35f4-r8w6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containers/buildah&lt;/p&gt;
&lt;p&gt;### Impact
With careful use of the `--mount` flag in RUN instructions in Containerfiles, and by using either multi-stage builds with use of concurrently-executing build stages (e.g., using the `--jobs` CLI flag) or multiple separate but concurrently-executing builds, a malicious Containerfile can be used to expose content from the build host to the command being run using the RUN instruction.  This can be used to read or write contents using the privileges of the process which is performing the build.  When that process is a root-owned podman system service which is provided for use by unprivileged users, this includes the ability to read and write contents which the client should not be allowed to read and write, including setuid executables in locations where they can be later accessed by unprivileged users.&lt;/p&gt;
&lt;p&gt;### Patches
Patches have been merged to the main branch, and will be added to upcoming releases on the release-1.38, release-1.37, release-1.35, and release-1.33 branches.&lt;/p&gt;
&lt;p&gt;This addressed a number of Jira cards, but primarily https://issues.redhat.com/browse/RHEL-67616 and https://issues.redhat.com/browse/RHEL-67618, which were then vendored into Podman and backported into olde rbranches.&lt;/p&gt;
&lt;p&gt;### Workarounds
Mandatory access controls should limit the access of the process performing the build, on systems where they are enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containers/buildah&lt;/p&gt;
&lt;p&gt;### Impact
With careful use of the `--mount` flag in RUN instructions in Containerfiles, and by using either multi-stage builds with use of concurrently-executing build stages (e.g., using the `--jobs` CLI flag) or multiple separate but concurrently-executing builds, a malicious Containerfile can be used to expose content from the build host to the command being run using the RUN instruction.  This can be used to read or write contents using the privileges of the process which is performing the build.  When that process is a root-owned podman system service which is provided for use by unprivileged users, this includes the ability to read and write contents which the client should not be allowed to read and write, including setuid executables in locations where they can be later accessed by unprivileged users.&lt;/p&gt;
&lt;p&gt;### Patches
Patches have been merged to the main branch, and will be added to upcoming releases on the release-1.38, release-1.37, release-1.35, and release-1.33 branches.&lt;/p&gt;
&lt;p&gt;This addressed a number of Jira cards, but primarily https://issues.redhat.com/browse/RHEL-67616 and https://issues.redhat.com/browse/RHEL-67618, which were then vendored into Podman and backported into olde rbranches.&lt;/p&gt;
&lt;p&gt;### Workarounds
Mandatory access controls should limit the access of the process performing the build, on systems where they are enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5vpc-35f4-r8w6</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-11218 — Podman: buildah: container breakout by using --jobs=2 and a race condition when building a malicious containerfile</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-11218</link>
      <description>msrc_CVE-2024-11218</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-11218</guid>
    </item>
    <item>
      <title>OESA-2025-2297 — buildah security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2297</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: buildah&lt;/p&gt;
&lt;p&gt;The  package provides a command line tool which can be used to * create a working container from scratch or * create a working container from an image as a starting point * mount/umount a working container&amp;amp;amp;apos;s root file system for manipulation * save container&amp;amp;amp;apos;s root file system layer to create a new image * delete a working container or an image&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.(CVE-2024-11218)&lt;/p&gt;
&lt;p&gt;Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that &amp;amp;quot;A call to this function does not guarantee that the key offered is in fact used to authenticate.&amp;amp;quot; Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make securit…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: buildah&lt;/p&gt;
&lt;p&gt;The  package provides a command line tool which can be used to * create a working container from scratch or * create a working container from an image as a starting point * mount/umount a working container&amp;amp;amp;apos;s root file system for manipulation * save container&amp;amp;amp;apos;s root file system layer to create a new image * delete a working container or an image&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.(CVE-2024-11218)&lt;/p&gt;
&lt;p&gt;Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that &amp;amp;quot;A call to this function does not guarantee that the key offered is in fact used to authenticate.&amp;amp;quot; Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make securit…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2297</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:14689-1 — podman-5.3.2-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:14689-1</link>
      <description>&lt;p&gt;podman-5.3.2-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;podman-5.3.2-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:14689-1</guid>
    </item>
    <item>
      <title>RHSA-2025:0830 — Red Hat Security Advisory: OpenShift Container Platform 4.16.33 packages and security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:0830</link>
      <description>&lt;p&gt;podman: buildah: Container breakout by using --jobs=2 and a race condition when building a malicious Containerfile jinja2: Jinja has a sandbox breakout through malicious filenames jinja2: Jinja has a sandbox breakout through indirect reference to format method&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;podman: buildah: Container breakout by using --jobs=2 and a race condition when building a malicious Containerfile jinja2: Jinja has a sandbox breakout through malicious filenames jinja2: Jinja has a sandbox breakout through indirect reference to format method&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:0830</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0297-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0297-1</link>
      <description>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:0297-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-11218</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-11218</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: podman, Ubuntu:26.04:LTS: podman&lt;/p&gt;
&lt;p&gt;A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: podman, Ubuntu:26.04:LTS: podman&lt;/p&gt;
&lt;p&gt;A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-11218</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0253 — Red Hat Enterprise Linux (Podman und Buildah): Schwachstelle ermöglicht Manipulation von Dateien</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0253</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0253</guid>
    </item>
  </channel>
</rss>
