CVE-2026-85747: Docker Distribution Client Manifest Integrity Bypass Vulnerability

Summary

15/10/2026
No i
Moderate
6.8

CVE-2026-85747: Distribution: Client manifests.Get() does not verify returned content against requested digest. Affects github.com/docker/distribution versions < 2.8.3. No fix is published. How to fix ↓

Also tracked for

The same CVE-2026-85747 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Docker Distribution package is a critical component used for managing Docker images and their associated metadata. It allows users to store and retrieve container images from a registry. This package is widely utilized in CI/CD pipelines and cloud-native applications, making its integrity crucial for maintaining secure software supply chains. The vulnerability in question arises from the client not verifying the integrity of manifests fetched by digest, potentially exposing users to malicious content.

Vulnerability Detail

The vulnerability occurs in the manifests.Get() function of the Docker Distribution client, which fetches a manifest by its digest but fails to verify the returned content against the requested digest. This oversight allows a malicious or compromised registry, or a man-in-the-middle (MITM) attacker, to serve arbitrary manifest data while falsely claiming it matches the requested digest. As a result, applications relying on digest pinning for supply-chain integrity are at risk, as they may unknowingly accept and act on tampered content.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, consider implementing additional validation checks in your application to verify the integrity of the manifest content against the expected digest before processing it. This can be done by manually computing the digest of the fetched content and comparing it with the requested digest.

Conclusion

CVE-2026-85747 represents a significant risk for applications using the Docker Distribution client due to its failure to verify manifest integrity. It is crucial for developers to update to the latest patched version and consider implementing additional validation checks to safeguard against potential exploitation.

See every vulnerability recorded for github.com/docker/distribution →

Share this vulnerability

FAQ

CVE-2026-85747 is a vulnerability in the Docker Distribution client that allows an attacker to serve arbitrary manifest content without proper integrity checks.

If your application relies on the Docker Distribution client to fetch manifests by digest, it may accept malicious content, undermining supply chain integrity.

An attacker could manipulate the content of Docker images, leading to unauthorized changes in application behavior, security breaches, or deployment of compromised software.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score of this vulnerability is 6.8, indicating a moderate severity level.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/docker/distribution.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback