Moby's external DNS requests from 'internal' networks could lead to data exfiltration

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-29018: 0.74% estimated exploitation activity in the next 30 days; percentile 54.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. 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. When containers with networking are created, they are assigned unique network interfaces…

Published by the source

20 Mar 2024, 17:59 UTC

Last modified by the source

20 Mar 2024, 17:59 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mq39-4gv4-mvpx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-29018

Advisory: Moby's external DNS requests from 'internal' networks could lead to data exfiltration
IDs: CVE-2024-29018, GHSA-mq39-4gv4-mvpx
Record: https://patchnext.com/advisories/cve-2024-29018 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/docker/docker 26.0.0-rc3, 25.0.5, 23.0.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/docker/docker: affected >= 26.0.0-rc1, < 26.0.0-rc3; >= 25.0.0, < 25.0.5; < 23.0.11; fixed in 26.0.0-rc3, 25.0.5, 23.0.11

## Suggested inspection (read-only)
- Go github.com/docker/docker: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/docker/docker.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mq39-4gv4-mvpx (GitHub-reviewed advisory GHSA-mq39-4gv4-mvpx lists affected ranges: Go github.com/docker/docker >=26.0.0-rc1 =25.0.0 =0 <23.0.11)

Commands are suggestions: review each one before running it.