← Back to results
Vulnerability record · public intelligence
CVE-2024-24557
MEDIUM

Classic builder cache poisoning

Published Feb 1, 2024 · Updated Oct 23, 2026 · Also known as GHSA-xw73-rw38-6vjc, GO-2024-2512

Severity · CVSSMEDIUM · 6.9
Known exploitationNot listed
EPSS / likelihood0.26%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Classic builder cache poisoning

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

The classic builder cache system is prone to cache poisoning if the image is built `FROM scratch`. Also, changes to some instructions (most important being `HEALTHCHECK` and `ONBUILD`) would not cause a cache miss.

Potential impact

23.0+ users are only affected if they explicitly opted out of Buildkit (DOCKERBUILDKIT=0 environment variable) or are using the /build API endpoint (which uses the classic builder by default). All users on versions older than 23.0 could be impacted. An example could be a CI with a shared cache, or just a regular Docker user pulling a malicious image due to misspelling/typosquatting. Image build API endpoint (/build) and ImageBuild function from github.com/docker/docker/client is also affected as it the uses classic builder by default.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
LOW
Confidence
Not available
Aliases
GHSA-xw73-rw38-6vjc, GO-2024-2512

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗

Record history

Published Feb 1, 2024 · Last refreshed Oct 23, 2026