<?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-02T15:26:49.199326+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-02382</id>
    <title>bdu:2024-02382</title>
    <updated>2026-10-02T15:26:49.537121+00:00</updated>
    <content>bdu:2024-02382</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2024-02382"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2024-29018</id>
    <title>BELL-CVE-2024-29018</title>
    <updated>2026-10-02T15:26:49.537165+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: docker, Alpaquita:stream: docker</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2024-29018"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0337</id>
    <title>certfr-2025-avi-0337 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
    <updated>2026-10-02T15:26:49.537194+00:00</updated>
    <content>certfr-2025-avi-0337</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0337"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-ac99204</id>
    <title>CLEANSTART-2026-AC99204 — Security fix for CVE-2024-29018 applied in: docker 26.0.0-r0, docker-fips 26.0.0-r0, paranoia 0.2.1-r0, rancher-agent 2…</title>
    <updated>2026-10-02T15:26:49.537211+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: docker, CleanStart: docker-fips, CleanStart: paranoia, CleanStart: rancher-agent</p>
<p>CVE-2024-29018 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-ac99204"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-158381</id>
    <title>EUVD-2026-158381</title>
    <updated>2026-10-02T15:26:49.537239+00:00</updated>
    <content>EUVD-2026-158381</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-158381"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-29018</id>
    <title>fkie_cve-2024-29018</title>
    <updated>2026-10-02T15:26:49.537251+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby's networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well.</p>
<p>When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.</p>
<p>Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly.</p>
<p>In addition to configuring the Linux kernel's various networking features to enable container networking, `dockerd` directly provides some services to container…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-29018"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mq39-4gv4-mvpx</id>
    <title>GHSA-mq39-4gv4-mvpx — Moby's external DNS requests from 'internal' networks could lead to data exfiltration</title>
    <updated>2026-10-02T15:26:49.537309+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/docker/docker</p>
<p>Moby is an open source container framework originally developed by Docker Inc. as Docker. It is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. As a batteries-included container runtime, Moby comes with a built-in networking implementation that enables communication between containers, and between containers and external resources.</p>
<p>Moby's networking implementation allows for creating and using many networks, each with their own subnet and gateway. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters, and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well.</p>
<p>When containers with networking are created, they are assigned unique network interfaces and IP addresses (typically from a non-routable [RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet). The root network namespace (hereafter referred to as the 'host') serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.</p>
<p>Containers on an _internal_ network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, a…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mq39-4gv4-mvpx"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2024-29018</id>
    <title>gsd-2024-29018</title>
    <updated>2026-10-02T15:26:49.537360+00:00</updated>
    <content>gsd-2024-29018</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2024-29018"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2024-29018</id>
    <title>msrc_CVE-2024-29018 — External DNS requests from 'internal' networks could lead to data exfiltration</title>
    <updated>2026-10-02T15:26:49.537372+00:00</updated>
    <content>msrc_CVE-2024-29018</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2024-29018"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2024-1417</id>
    <title>OESA-2024-1417 — docker security update</title>
    <updated>2026-10-02T15:26:49.537387+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: docker</p>
<p>Docker is an open source project to build, ship and run any application as a lightweight container.

Security Fix(es):

Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby&amp;apos;s networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well.

When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.

Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly.

In addition to configurin…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2024-1417"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14597-1</id>
    <title>openSUSE-SU-2024:14597-1 — docker-27.4.1_ce-12.1 on GA media</title>
    <updated>2026-10-02T15:26:49.537426+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>docker-27.4.1_ce-12.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2024:14597-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2024:7164</id>
    <title>RHSA-2024:7164 — Red Hat Security Advisory: Migration Toolkit for Containers (MTC) 1.8.4 security and bug fix update</title>
    <updated>2026-10-02T15:26:49.537442+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>github.com/gin-contrib/cors: Gin mishandles a wildcard in the origin string in github.com/gin-contrib/cors golang: net/http, x/net/http2: unlimited number of CONTINUATION frames causes DoS golang: net/http/cookiejar: incorrect forwarding of sensitive headers and cookies on HTTP redirect containers/image: digest type does not guarantee valid type braces: fails to limit the number of characters it can handle golang: net: malformed DNS message can cause infinite loop jose-go: improper handling of highly compressed data follow-redirects: Possible credential leak node-tar: denial of service while parsing a tar file due to lack of folders depth validation moby: external DNS requests from 'internal' networks could lead to data exfiltration express: cause malformed URLs to be evaluated webpack-dev-middleware: lack of URL validation may lead to file leak axios: axios: Server-Side Request Forgery</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2024:7164"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:0226-1</id>
    <title>SUSE-SU-2025:0226-1 — Security update for docker-stable</title>
    <updated>2026-10-02T15:26:49.537480+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for docker-stable</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2025:0226-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-29018</id>
    <title>UBUNTU-CVE-2024-29018</title>
    <updated>2026-10-02T15:26:49.537496+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: docker.io, 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, Ubuntu:22.04:LTS: docker.io-app, Ubuntu:Pro:22.04:LTS: docker.io-app, Ubuntu:24.04:LTS: docker.io, Ubuntu:24.04:LTS: docker.io-app, Ubuntu:Pro:24.04:LTS: docker.io-app</p>
<p>Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby's networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well. When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs. Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly. In addition to configuring the Linux kernel's various networking features to enable container networking, `dockerd` directly provides some services to container ne…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-29018"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0684</id>
    <title>WID-SEC-W-2024-0684 — docker: Schwachstelle ermöglicht Offenlegung von Informationen</title>
    <updated>2026-10-02T15:26:49.537545+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in docker ausnutzen, um Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0684"/>
  </entry>
</feed>
