<?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-03T01:48:36.095191+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/bdu:2024-01030</id>
    <title>bdu:2024-01030</title>
    <updated>2026-10-03T01:48:36.464804+00:00</updated>
    <content>bdu:2024-01030</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2024-01030"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2024-23653</id>
    <title>BELL-CVE-2024-23653</title>
    <updated>2026-10-03T01:48:36.464867+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: podman, Alpaquita:stream: docker, Alpaquita:stream: podman</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2024-23653"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0841</id>
    <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>
    <updated>2026-10-03T01:48:36.464902+00:00</updated>
    <content>certfr-2024-avi-0841</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2024-avi-0841"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2025-hp29789</id>
    <title>CLEANSTART-2025-HP29789 — BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner</title>
    <updated>2026-10-03T01:48:36.464920+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: buildkit, CleanStart: buildkitd</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2025-hp29789"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-159744</id>
    <title>EUVD-2026-159744</title>
    <updated>2026-10-03T01:48:36.464947+00:00</updated>
    <content>EUVD-2026-159744</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-159744"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-23653</id>
    <title>fkie_cve-2024-23653</title>
    <updated>2026-10-03T01:48:36.464959+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-23653"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wr6v-9f75-vh2g</id>
    <title>GHSA-wr6v-9f75-vh2g — Buildkit's interactive containers API does not validate entitlements check</title>
    <updated>2026-10-03T01:48:36.464984+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/moby/buildkit</p>
<p>### 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.</p>
<p>### Patches
The issue has been fixed in v0.12.5 .</p>
<p>### 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.</p>
<p>### References</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wr6v-9f75-vh2g"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2024-23653</id>
    <title>gsd-2024-23653</title>
    <updated>2026-10-03T01:48:36.465011+00:00</updated>
    <content>gsd-2024-23653</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2024-23653"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2024-23653</id>
    <title>msrc_CVE-2024-23653 — BuildKit interactive containers API does not validate entitlements check</title>
    <updated>2026-10-03T01:48:36.465023+00:00</updated>
    <content>msrc_CVE-2024-23653</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2024-23653"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13688-1</id>
    <title>openSUSE-SU-2024:13688-1 — buildkit-0.12.5-2.1 on GA media</title>
    <updated>2026-10-03T01:48:36.465040+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>buildkit-0.12.5-2.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2024:13688-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2024:0587-1</id>
    <title>SUSE-SU-2024:0587-1 — Security update for docker</title>
    <updated>2026-10-03T01:48:36.465056+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for docker</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2024:0587-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-23653</id>
    <title>UBUNTU-CVE-2024-23653</title>
    <updated>2026-10-03T01:48:36.465073+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-23653"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0272</id>
    <title>WID-SEC-W-2024-0272 — docker: Mehrere Schwachstellen</title>
    <updated>2026-10-03T01:48:36.465105+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0272"/>
  </entry>
</feed>
