CVE-2026-85747: Docker registry · Distribution is a toolkit to pack, ship, store, and deliver container content
Affects docker-registrySource GCVE Database
Not known to be exploited · CVSS 6.8 Medium · fixed in 3.1.2 : update docker-registry when convenient.
Data as of 28 Oct 2026, 22:28 UTC
- Patch
- Available – fixed in 3.1.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10docker-registrypkg:deb/ubuntu/docker-registry?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu Pro 26.04 LTSdocker-registrypkg:deb/ubuntu/docker-registry?arch=source&distro=esm-apps/resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSdocker-registrypkg:deb/ubuntu/docker-registry?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSdocker-registrypkg:deb/ubuntu/docker-registry?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSdocker-registrypkg:deb/ubuntu/docker-registry?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSdocker-registrypkg:deb/ubuntu/docker-registry?arch=source&distro=esm-apps/bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.2, registry/client.(*manifests).Get() reads a manifest returned for a digest-pinned request and passes it to distribution.UnmarshalManifest without hashing the body against the requested digest, allowing a malicious or intercepted registry response to substitute attacker-chosen manifest content even when Docker-Content-Digest claims the requested value. The bundled pull-through proxy in registry/proxy/proxymanifeststore.go can cache and re-serve the substituted manifest. This issue is fixed in version 3.1.2.
References
- ubuntu.com/security/CVE-2026-85747 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-85747 (opens in a new tab)
- github.com/distribution/distribution/security/advisories/GHSA-685w-q87j-wqw3 (opens in a new tab)
- github.com/distribution/distribution/commit/960439b09f342cdeb8f1c0e18e8c7349bdcfbf80 (opens in a new tab)
- github.com/distribution/distribution/releases/tag/v3.1.2 (opens in a new tab)