# Classic builder cache poisoning Advisory record · `GHSA-xw73-rw38-6vjc` - **Identifiers:** `GHSA-xw73-rw38-6vjc` · `CVE-2024-24557` · `GO-2024-2512` - **State:** Confirmed - **Severity:** CVSS 6.9 Medium - **Critical:** No - **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html) · [CWE-346](https://cwe.mitre.org/data/definitions/346.html) - **Tags:** [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md) · [CWE-346](https://agentprime.io/advisories/tag/cwe-346.md) - **Published:** 1 Feb 2024 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 1 Feb 2024, 20:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/docker/docker` (Go): affected `<24.0.9 || >=25.0.0, <25.0.2`; fixed in `24.0.9`, `25.0.2` - `github.com/moby/moby` (Go): affected `<24.0.9 || >=25.0.0, <25.0.2`; fixed in `24.0.9`, `25.0.2` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Docker and Moby (github.com/docker/docker and github.com/moby/moby) versions below 24.0.9, and versions 25.0.0 up to but not including 25.0.2, are vulnerable to build cache poisoning in the classic builder. An attacker who knows a user's Dockerfile can supply a crafted image that is accepted as a valid cache for build steps, so a build may run a substituted instruction such as a different HEALTHCHECK. Upgrade to 24.0.9 or 25.0.2. Builds can also avoid the classic builder by using BuildKit or passing --no-cache. 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 - 6.9 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0026, the 17th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 1 Feb 2024, 03:58 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/moby/moby/security/advisories/GHSA-xw73-rw38-6vjc) - 31 Oct 2026, 14:15 UTC: First seen by agentprime - 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xw73-rw38-6vjc) ## Sources - [GitHub Advisory Database: GHSA-xw73-rw38-6vjc](https://github.com/advisories/GHSA-xw73-rw38-6vjc) - [OSV: GHSA-xw73-rw38-6vjc](https://osv.dev/vulnerability/GHSA-xw73-rw38-6vjc) - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .