Improper Validation of Integrity Check Value Affecting github.com/distribution/distribution/v3/internal/client package, versions <3.1.2
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMDISTRIBUTIONDISTRIBUTIONV3INTERNALCLIENT-20969954
- published15 Oct 2026
- disclosed13 Oct 2026
- creditKris Kennaway
Introduced: 13 Oct 2026
NewCVE-2026-85747 Â (opens in a new tab)How to fix?
Upgrade github.com/distribution/distribution/v3/internal/client to version 3.1.2 or higher.
Overview
Affected versions of this package are vulnerable to Improper Validation of Integrity Check Value in the Get method of the manifests type in registry/client/repository.go, which reads the response body and passes it to distribution.UnmarshalManifest without computing digest.FromBytes(body) and comparing it against the digest the caller requested. An attacker who controls the registry endpoint or holds a MitM position on the connection can substitute arbitrary manifest content for a digest-pinned request, setting Docker-Content-Digest to the requested value, since that header is server supplied and is only used to populate the ReturnContentDigest out-parameter rather than recomputed from the body. The substitution is undetectable to callers that rely on digest pinning for integrity, and the bundled pull-through cache in registry/proxy/proxymanifeststore.go writes the returned manifest straight to local storage without re-verifying it, so a poisoned response persists in the mirror for every later consumer.