Summary
Workarounds
Ensure you only pull images from trusted sources.
References
https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
For more information
If you have any questions or comments about this advisory:
- Open an issue in
- Email us at [email protected]
Impact
In the OCI Distribution Specification version 1.0.0 and prior and in the OCI Image Specification version 1.0.1 and prior, manifest and index documents are ambiguous without an accompanying Content-Type HTTP header. Versions of Moby (Docker Engine) prior to 20.10.11 treat the Content-Type header as trusted and deserialize the document according to that header. If the Content-Type header changed between pulls of the same ambiguous document (with the same digest), the document may be interpreted differently, meaning that the digest alone is insufficient to unambiguously identify the content of the image.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
This issue has been fixed in Moby (Docker Engine) 20.10.11. Image pulls for manifests that contain a “manifests” field or indices which contain a “layers” field are rejected.
Frequently Asked Questions
- What is GHSA-XMMX-7JPF-FX42? GHSA-XMMX-7JPF-FX42 is a medium-severity security vulnerability in github.com/docker/docker (go), affecting versions < 20.10.11. It is fixed in 20.10.11.
- Which packages are affected by GHSA-XMMX-7JPF-FX42?
github.com/docker/docker(go) (versions < 20.10.11)github.com/moby/moby(go) (versions < 20.10.11)
- Is there a fix for GHSA-XMMX-7JPF-FX42? Yes. GHSA-XMMX-7JPF-FX42 is fixed in 20.10.11. Upgrade to this version or later.
- Is GHSA-XMMX-7JPF-FX42 exploitable, and should I be worried? Whether GHSA-XMMX-7JPF-FX42 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-XMMX-7JPF-FX42 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-XMMX-7JPF-FX42?
- Upgrade
github.com/docker/dockerto 20.10.11 or later - Upgrade
github.com/moby/mobyto 20.10.11 or later
- Upgrade