CVE-2024-32473 | Moby IPv6 enabled on IPv4-only network interfaces

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. In 26.0.0, IPv6 is not disabled on network interfaces, including those belonging to networks where `--ipv6=false`. An container with an `ipvlan` or `macvlan` interface will normally be configured to share an external network link with the host machine. Because of this direct access, (1) Containers may be able to communicate with other hosts on the local network over link-local IPv6 addresses, (2) if router advertisements are being broadcast over the local network, containers may get SLAAC-assigned addresses, and (3) the interface will be a member of IPv6 multicast groups. This means interfaces in IPv4-only networks present an unexpectedly and unnecessarily increased attack surface. The issue is patched in 26.0.2. To completely disable IPv6 in a container, use `--sysctl=net.ipv6.conf.all.disable_ipv6=1` in the `docker create` or `docker run` command. Or, in the service configuration of a `compose` file.

Published: 2024-04-18 Last update: 2025-09-04 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-32473 is rated Low Risk (28.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.09%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-32473

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-09-05 0.01% 0.09% +0.08%
2 2025-04-15 0.06% 0.01% -0.05%
3 2025-03-30 0.06%

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-32473

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.0 3.6 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 3.6 [email protected]

Weakness enumeration for CVE-2024-32473

GitHub Security Advisory for CVE-2024-32473

GHSA-x84c-p2g9-rqv9 · Severity: medium · Ecosystem: go — IPv6 enabled on IPv4-only network interfaces

OS Trackers for CVE-2024-32473

vendor priority summary link
alpine CVE-2024-32473: 1 source package rows (docker); 4 state rows across 4 repos (3.20-community, 3.21-community, 3.22-community, edge-community); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2024-32473
debian not yet assigned CVE-2024-32473 not yet assigned priority: Debian including 1 source packages (docker.io), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2024-32473
redhat medium https://access.redhat.com/security/cve/CVE-2024-32473
suse medium CVE-2024-32473 severity moderate: SUSE including 7 source package names (docker, docker-bash-completion, …), 81 product×package rows across 25 product lines (SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (25 product lines)): Known Not Affected 81. https://www.suse.com/security/cve/CVE-2024-32473/
ubuntu medium CVE-2024-32473 medium priority: Ubuntu including 2 source packages (docker.io, docker.io-app), 18 status rows across 10 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, upstream, xenial): not-affected 12, released 4, ignored 2. https://ubuntu.com/security/CVE-2024-32473

Affected software / configurations for CVE-2024-32473

Vendor Product Version Raw CPE
mobyproject moby >= 26.0.0, < 26.0.2 cpe:2.3:a:mobyproject:moby:*:*:*:*:*:*:*:*

References for CVE-2024-32473

cvelogic Threat Intelligence