Is CVE-2026-85747 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-85747 being exploited in the wild.

How severe is CVE-2026-85747?

Medium severity, with a CVSS score of 6.8, published 13 October 2026.

Which products and versions are affected?

Docker Distribution 2.8.3 and earlier; github.com/distribution/distribution (Go) SEMVER:introduced=0; github.com/distribution/distribution/v3 (Go) < 3.1.2, SEMVER:introduced=0,fixed=3.1.2; github.com/docker/distribution (Go) <= 2.8.3, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.8.3.

Is there a fix for CVE-2026-85747?

Yes. github.com/distribution/distribution/v3 (Go): upgrade to 3.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-85747 attacked?

It is attacked over the network or from the adjacent network, in a software library.

Am I affected by CVE-2026-85747?

Check whether you run Docker Distribution, github.com/distribution/distribution (Go), github.com/distribution/distribution/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-85747: Docker Distribution client manifests.Get() digest verification bypass

Q: Is there a fix for CVE-2026-85747?

Yes. github.com/distribution/distribution/v3 (Go): upgrade to 3.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-85747 attacked?

It is attacked over the network or from the adjacent network, in a software library.

Q: Am I affected by CVE-2026-85747?

Check whether you run Docker Distribution, github.com/distribution/distribution (Go), github.com/distribution/distribution/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-85747 · Severity: medium · CVSS 6.8 · Published 2026-10-13

Docker Distribution's client library, which retrieves container image manifests from registries, does not verify that the returned manifest matches the requested digest hash. A malicious or compromised registry can serve an attacker-chosen manifest while claiming it matches the pinned digest, allowing supply-chain attacks that bypass image policy controls and poison cache servers with malicious images.

Technologies: github.com/distribution/distribution (Go), github.com/distribution/distribution/v3 (Go), github.com/docker/distribution (Go). Vendors: Docker, Go.

Quick answers

Is CVE-2026-85747 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-85747 being exploited in the wild.
How severe is CVE-2026-85747?: Medium severity, with a CVSS score of 6.8, published 13 October 2026.
Which products and versions are affected?: Docker Distribution 2.8.3 and earlier; github.com/distribution/distribution (Go) SEMVER:introduced=0; github.com/distribution/distribution/v3 (Go) < 3.1.2, SEMVER:introduced=0,fixed=3.1.2; github.com/docker/distribution (Go) <= 2.8.3, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.8.3.
Is there a fix for CVE-2026-85747?: Yes. github.com/distribution/distribution/v3 (Go): upgrade to 3.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85747 attacked?: It is attacked over the network or from the adjacent network, in a software library.
Am I affected by CVE-2026-85747?: Check whether you run Docker Distribution, github.com/distribution/distribution (Go), github.com/distribution/distribution/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/distribution/distribution/v3 (Go): upgrade to 3.1.2 or later
```
go get github.com/distribution/distribution/v3@v3.1.2
```

Technical details

The vulnerability exists in `registry/client.(*manifests).Get()` which reads the HTTP response body without computing `digest.FromBytes(body)` and comparing it against the caller-supplied digest parameter. Only the server-supplied `Docker-Content-Digest` header is parsed, which an attacker can forge. The attack requires network-level control or MITM position on the registry connection; image policy controllers and pull-through proxies that rely on digest pinning are directly exploitable.

Affected products

Docker Distribution 2.8.3 and earlier

Identifiers

CVE-2026-85747
BIT-DISTRIBUTION-2026-85747
GHSA-685w-q87j-wqw3
GO-2026-6778

Timeline

2026-10-15: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.