<?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 08:07:25 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-01030</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-01030</link>
      <description>bdu:2024-01030</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-01030</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-23653</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-23653</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: podman, Alpaquita:stream: docker, Alpaquita:stream: podman&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: podman, Alpaquita:stream: docker, Alpaquita:stream: podman&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-23653</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0841 — 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-2024-avi-0841</link>
      <description>certfr-2024-avi-0841</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0841</guid>
    </item>
    <item>
      <title>CLEANSTART-2025-HP29789 — BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2025-hp29789</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: buildkit, CleanStart: buildkitd&lt;/p&gt;
&lt;p&gt;CVE-2024-23653 affects multiple packages. BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: buildkit, CleanStart: buildkitd&lt;/p&gt;
&lt;p&gt;CVE-2024-23653 affects multiple packages. BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2025-hp29789</guid>
    </item>
    <item>
      <title>EUVD-2026-159744</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-159744</link>
      <description>EUVD-2026-159744</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-159744</guid>
    </item>
    <item>
      <title>fkie_cve-2024-23653</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-23653</link>
      <description>&lt;p&gt;BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-23653</guid>
    </item>
    <item>
      <title>GHSA-wr6v-9f75-vh2g — Buildkit's interactive containers API does not validate entitlements check</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wr6v-9f75-vh2g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/moby/buildkit&lt;/p&gt;
&lt;p&gt;### Impact
In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.&lt;/p&gt;
&lt;p&gt;### Patches
The issue has been fixed in v0.12.5 .&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using BuildKit frontends from untrusted sources. A frontend image is usually specified as the `#syntax` line on your Dockerfile, or with `--frontend` flag when using `buildctl build` command.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/moby/buildkit&lt;/p&gt;
&lt;p&gt;### Impact
In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request.&lt;/p&gt;
&lt;p&gt;### Patches
The issue has been fixed in v0.12.5 .&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using BuildKit frontends from untrusted sources. A frontend image is usually specified as the `#syntax` line on your Dockerfile, or with `--frontend` flag when using `buildctl build` command.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wr6v-9f75-vh2g</guid>
    </item>
    <item>
      <title>gsd-2024-23653</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-23653</link>
      <description>gsd-2024-23653</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-23653</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-23653 — BuildKit interactive containers API does not validate entitlements check</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-23653</link>
      <description>msrc_CVE-2024-23653</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-23653</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:13688-1 — buildkit-0.12.5-2.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13688-1</link>
      <description>&lt;p&gt;buildkit-0.12.5-2.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;buildkit-0.12.5-2.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:13688-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:0587-1 — Security update for docker</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:0587-1</link>
      <description>&lt;p&gt;Security update for docker&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for docker&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:0587-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-23653</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-23653</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: docker.io, Ubuntu:Pro:20.04:LTS: docker.io, Ubuntu:Pro:20.04:LTS: docker.io-app, Ubuntu:22.04:LTS: docker.io-app, Ubuntu:Pro:22.04:LTS: docker.io, Ubuntu:24.04:LTS: docker.io-app, Ubuntu:Pro:24.04:LTS: docker.io&lt;/p&gt;
&lt;p&gt;BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: docker.io, Ubuntu:Pro:20.04:LTS: docker.io, Ubuntu:Pro:20.04:LTS: docker.io-app, Ubuntu:22.04:LTS: docker.io-app, Ubuntu:Pro:22.04:LTS: docker.io, Ubuntu:24.04:LTS: docker.io-app, Ubuntu:Pro:24.04:LTS: docker.io&lt;/p&gt;
&lt;p&gt;BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-23653</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0272 — docker: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0272</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen in Docker ausnutzen, um seine Privilegien zu erhöhen, einen Denial-of-Service-Zustand zu verursachen, vertrauliche Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen in Docker ausnutzen, um seine Privilegien zu erhöhen, einen Denial-of-Service-Zustand zu verursachen, vertrauliche Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0272</guid>
    </item>
  </channel>
</rss>
