# IPv6 enabled on IPv4-only network interfaces

Advisory record · `GHSA-x84c-p2g9-rqv9`

- **Identifiers:** `GHSA-x84c-p2g9-rqv9` · `CVE-2024-32473` · `GO-2024-2737`
- **State:** Confirmed
- **Severity:** CVSS 4.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-668](https://cwe.mitre.org/data/definitions/668.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 18 Apr 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Apr 2024, 21:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/docker/docker` (Go): affected `>=26.0.0, <26.0.2`; fixed in `26.0.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Docker Engine (github.com/docker/docker) versions 26.0.0 and 26.0.1 leave IPv6 enabled on network interfaces even in networks created with IPv6 turned off. An attacker on the local network, or a container with an ipvlan or macvlan interface, could reach hosts over link-local IPv6, receive SLAAC addresses from router advertisements, or send malicious router advertisements. Upgrade to 26.0.2. Until then, setting the sysctl net.ipv6.conf.all.disable_ipv6 to 1 on containers disables IPv6 for them.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.7 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 18 Apr 2024, 20:44 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/moby/moby/security/advisories/GHSA-x84c-p2g9-rqv9)
- 31 Oct 2026, 14:15 UTC: First seen by agentprime
- 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x84c-p2g9-rqv9)

## Sources

- [GitHub Advisory Database: GHSA-x84c-p2g9-rqv9](https://github.com/advisories/GHSA-x84c-p2g9-rqv9)
- [OSV: GHSA-x84c-p2g9-rqv9](https://osv.dev/vulnerability/GHSA-x84c-p2g9-rqv9)
- <https://github.com/moby/moby/security/advisories/GHSA-x84c-p2g9-rqv9>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-32473>
- <https://github.com/moby/moby/commit/7cef0d9cd1cf221d8c0b7b7aeda69552649e0642>
- <https://github.com/moby/moby>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x84c-p2g9-rqv9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x84c-p2g9-rqv9/>. Everything for agents: <https://agentprime.io/llms.txt>.
