ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-85747

Distribution: Client does not verify returned content against requested digest

Published Oct 13, 2026 · catalog updated Oct 18, 2026 · Distribution: Client does not

Check if you run it

No confirmed exploitation is on record for CVE-2026-85747. EPSS is 0.21%. Act only if a listed version of Distribution: Client does not is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Distribution: Client does not).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.21%
Remediation
Version ranges on file
Affected products
go github.com/distribution/distribution/v3 · go github.com/docker/distribution · golang github.com · package golang

### Summary fetches a manifest by digest but never hashes the returned body and compares it against the requested digest. A malicious or compromised registry, or any MITM on the registry connection, can serve arbitrary manifest bytes in response to a digest-pinned request and the client returns the substituted content transparently to the caller. Any application relying on digest pinning for supply-chain integrity — image policy controllers, mirrors, pull-through caches — is silently undermined. The bundled pull-through proxy ( ) is itself an unguarded consumer and is directly exploitable. ### Details **Root cause:** reads the response body and passes it directly to without ever computing and comparing against the caller-supplied . The response header is parsed (lines 251-292 in ) only to populate an out-parameter ( ) and is itself server-supplied — it is never recomputed from the body, so a lying server can set it to whatever value the caller requested while delivering different bytes. **Attack path:** An attacker who controls the registry endpoint (malicious registry, compromised upstream, DNS hijack, or TLS MITM) responds to with: 1. (forged header) 2. A body containing a different, attacker-chosen manifest The client calls on the substituted body, returns the attacker's manifest as if it were the pinned content, and the caller has no way to detect the substitution. **Why it matters:** The entire value of digest pinning is to guarantee content-addressable integrity against exactly this threat model (hostile or MITM server). The pull-through cache calls and immediately writes the result to local storage with no re-verification — so a poisoned remote can permanently inject a bad manifest into the mirror cache, affecting all subsequent consumers. Relevant code path ( , simplified): ### PoC **go.mod:** **main.go:** **Output (v2.8.3+incompatible):** ### Impact Any application that calls with a digest argument — and relies on that digest to guarantee which image conten

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • go github.com/distribution/distribution/v3< 3.1.2
  • go github.com/docker/distribution<= 2.8.3
  • golang github.comversion unspecified
  • package golangversion unspecified

How to fix CVE-2026-85747

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-85747. EPSS is 0.21%. Act only if a listed version of Distribution: Client does not is installed.

Which versions are affected?

Compare what you have installed with < 3.1.2, <= 2.8.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-354. EPSS 0.21%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 15, 2026 · GitHub Advisory Database

    Detected

    ### Summary fetches a manifest by digest but never hashes the returned body and compares it against the requested digest. A malicious or compromised registry, or any MITM on the registry connection, can serve arbitrary manifest bytes in response to a digest-pinned request and the client returns the substituted content transparently to the caller. Any application relying on digest pinning for suppl

  2. Oct 15, 2026 · GitHub Advisory Database

    Updated

    ### Summary fetches a manifest by digest but never hashes the returned body and compares it against the requested digest. A malicious or compromised registry, or any MITM on the registry connection, can serve arbitrary manifest bytes in response to a digest-pinned request and the client returns the substituted content transparently to the caller. Any application relying on digest pinning for suppl

  3. Oct 18, 2026 · NIST NVD

    Updated

    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 Do

Sources

  • CVE.orgVulnerability recordCVE-2026-85747

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-85747

    30-day exploitation probability 0.2%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-685w-q87j-wqw3

    Distribution: Client does not verify returned content against requested digest

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-85747

    registry/client.(*manifests).Get(ctx, dgst, …) fetches a manifest by digest but never hashes the returned body and compares it against the requested digest. A malicious or compromised registry, or any MITM on the registry connection, can serve arbitrary manifest bytes in response to a digest-pinned request and the client returns the substituted content transparently to the caller. Any application

    advisories.gitlab.com
  • NIST NVDVulnerability recordCVE-2026-85747

    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 d

    nvd.nist.gov
  • Snyk Vulnerability DatabasePackage advisorySNYK-GOLANG-GITHUBCOMDISTRIBUTIONDISTRIBUTIONINTERNALCLIENT-20969953

    Improper Validation of Integrity Check Value

    security.snyk.io
  • Snyk Vulnerability DatabasePackage advisorySNYK-GOLANG-GITHUBCOMDISTRIBUTIONDISTRIBUTIONV3INTERNALCLIENT-20969954

    Improper Validation of Integrity Check Value

    security.snyk.io

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.