Moby (Docker Engine) is vulnerable to Ambiguous OCI manifest parsing

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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. Patches 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. Workarounds Ensure you only pull images from trusted sources. References https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m…

Published by the source

10 Jun 2024, 18:39 UTC

Last modified by the source

5 Jul 2024, 20:52 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xmmx-7jpf-fx42

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-xmmx-7jpf-fx42

Advisory: Moby (Docker Engine) is vulnerable to Ambiguous OCI manifest parsing
IDs: GHSA-xmmx-7jpf-fx42
Record: https://patchnext.com/advisories/ghsa-xmmx-7jpf-fx42 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/docker/docker 20.10.11; github.com/moby/moby 20.10.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/docker/docker: affected < 20.10.11; fixed in 20.10.11
- Go github.com/moby/moby: affected < 20.10.11; fixed in 20.10.11

## Suggested inspection (read-only)
- Go github.com/docker/docker: check the installed version with your package manager.
- Go github.com/moby/moby: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/docker/docker, github.com/moby/moby.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xmmx-7jpf-fx42 (GitHub-reviewed advisory GHSA-xmmx-7jpf-fx42 lists affected ranges: Go github.com/docker/docker >=0 =0 <20.10.11)

Commands are suggestions: review each one before running it.