CVE-2026-85747: 
cAdvisor Analyse et atténuation de la vulnérabilité

Aperçu

CVE-2026-85747 is a manifest digest verification bypass vulnerability in the Distribution toolkit (the OCI/Docker container registry library). The registry/client.(*manifests).Get() function fetches a manifest by digest but never hashes the returned body against the requested digest, allowing a malicious or intercepted registry to substitute arbitrary manifest content while the Docker-Content-Digest header claims the correct value. Affected versions are github.com/distribution/distribution/v3 prior to 3.1.2 and github.com/docker/distribution up to and including v2.8.3. The vulnerability was disclosed on September 23, 2026, and published to the GitHub Advisory Database on October 15, 2026. It carries a CVSS v3.1 base score of 6.8 (Medium) (Github Advisory, GitHub Security Advisory).

Détails techniques

The root cause is classified as CWE-354 (Improper Validation of Integrity Check Value). In registry/client/repository.go (lines 488–505), the response body is read and passed directly to distribution.UnmarshalManifest without computing digest.FromBytes(body) and comparing it against the caller-supplied digest. The Docker-Content-Digest response header is parsed only to populate an out-parameter (ReturnContentDigest) and is never recomputed from the body — a lying server can set it to any value while delivering different bytes. The bundled pull-through proxy in registry/proxy/proxymanifeststore.go (lines 42–87) calls remoteManifests.Get(ctx, dgst) and immediately writes the result to local storage with no re-verification, enabling permanent cache poisoning of the mirror. A complete, runnable Go PoC (main.go) is publicly available in the security advisory, demonstrating the bypass using an httptest.NewServer that serves a forged manifest with a spoofed Docker-Content-Digest header (Github Advisory, GitHub Security Advisory).

Impact

Successful exploitation allows an attacker to silently substitute arbitrary container image manifest content — including changing image layers, entrypoints, or referenced blobs — for any client performing digest-pinned pulls. The scope is changed (CVSS S:C) because the pull-through proxy can cache and re-serve the poisoned manifest to all downstream consumers, amplifying the impact beyond the initially targeted client. Affected asset classes include image policy controllers enforcing allowed digests, pull-through cache/mirror implementations, and CI/CD pipelines that pin images by digest for supply-chain integrity. There is no confidentiality or availability impact, but the integrity impact is high, as the fundamental guarantee of content-addressable digest pinning is completely undermined (Github Advisory, GitHub Security Advisory).

Exploitabilité

A complete, runnable proof-of-concept exploit written in Go is publicly available within the GitHub Security Advisory (GHSA-685w-q87j-wqw3), confirmed with high confidence by Feedly's exploit analysis. The PoC demonstrates the bypass against github.com/docker/distribution v2.8.3+incompatible using a mock malicious registry server. As of the time of reporting, there is no evidence of in-the-wild exploitation. The EPSS score is approximately 0.218% (12th percentile), indicating a low but non-negligible probability of exploitation in the near term. The vulnerability is not currently listed in the CISA KEV catalog, and no threat actor attribution has been reported (Github Advisory, GitHub Security Advisory).

Étapes d’exploitation

  1. Gain a position to intercept or control the registry endpoint: Achieve a man-in-the-middle position on the TLS connection between the victim client and its configured registry (e.g., via DNS hijacking, BGP hijacking, or a compromised upstream registry), or operate a malicious registry that the victim is configured to pull from.
  2. Prepare two manifests: Create a trustedManifest (the content the victim expects, whose SHA-256 digest is the pinned value) and an evilManifest (attacker-controlled content with different layer/config references). Compute pinnedDigest = sha256(trustedManifest) and evilDigest = sha256(evilManifest).
  3. Intercept the digest-pinned manifest request: When the victim client issues GET /v2/{name}/manifests/{pinnedDigest}, intercept or handle the request at the attacker-controlled registry endpoint.
  4. Serve the forged response: Respond with HTTP 200, setting Content-Type: application/vnd.docker.distribution.manifest.v2+json, Docker-Content-Digest: {pinnedDigest} (forged to match what was requested), and a body containing the bytes of evilManifest.
  5. Client accepts substituted content: The vulnerable registry/client.(*manifests).Get() reads the body and passes it to distribution.UnmarshalManifest without hashing it against pinnedDigest. The attacker's manifest is returned to the caller as if it were the pinned content.
  6. Cache poisoning (optional amplification): If the victim uses the bundled pull-through proxy (registry/proxy/proxymanifeststore.go), the poisoned manifest is written to local storage and re-served to all downstream clients without re-verification, permanently injecting the malicious manifest into the mirror cache (Github Advisory, GitHub Security Advisory).

Indicateurs de compromis

  • Network: Unexpected or anomalous responses to GET /v2/{name}/manifests/{digest} requests where the Docker-Content-Digest response header value does not match the SHA-256 hash of the response body; outbound connections from registry hosts to unexpected upstream endpoints.
  • Logs: Registry client logs showing manifests fetched by digest where the returned content digest differs from the requested digest (detectable only after patching, which adds explicit error logging); pull-through proxy cache logs recording manifest writes from remote sources at unusual times or from unexpected upstream registries.
  • File System: Unexpected or modified manifest files in the pull-through proxy's local cache storage directory; container image layers or configs referencing unknown or attacker-controlled blob digests.
  • Process/Runtime: Containers launched from images whose manifest digest does not match the pinned digest specified in deployment configurations; image policy controller alerts on digest mismatches (if the controller independently verifies digests outside the vulnerable library) (Github Advisory).

Atténuation et solutions de contournement

The primary remediation is to upgrade to github.com/distribution/distribution/v3 version 3.1.2 or later, which adds explicit digest verification in registry/client.(*manifests).Get() by computing dgst.Verifier() over the response body before passing it to UnmarshalManifest, and similarly hardens blobs.Get(). The legacy github.com/docker/distribution module (v2.8.x) has no patched version available; users should migrate to the v3 module. As interim mitigations, enforce TLS with certificate pinning between clients and registries to reduce MITM risk, implement network segmentation to restrict registry access, and independently verify manifest digests on the client side before deploying containers. Monitor pull-through proxy caches for unexpected manifest content (GitHub Release, Github Advisory).

Réactions de la communauté

The vulnerability was reported by security researcher KrisKennawayDD and published by maintainer milosgajdos. Coverage appeared in Linux security roundup newsletters and German Linux security news outlet Pro-Linux.de. The fix was merged and released as part of the v3.1.2 patch release, which the maintainers described as a stable release with security fixes. No major vendor statements beyond the GitHub advisory or significant social media controversy have been identified (GitHub Release).

Ressources supplémentaires

État de correction de la distribution Linux

Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.

Debian

Affecté

bookworm

docker-registry

Affecté

sid

docker-registry

Affecté

trixie

docker-registry

Affecté

Ubuntu

Inconnu

bionic (esm-apps)

docker-registry

Inconnu

devel

docker-registry

Inconnu

focal (esm-apps)

docker-registry

Inconnu

jammy

docker-registry

Inconnu

jammy (esm-apps)

docker-registry

Inconnu

noble

docker-registry

Inconnu

noble (esm-apps)

docker-registry

Inconnu

resolute

docker-registry

Inconnu

RHEL / CentOS

Inconnu

Source: Ce rapport a été généré à l’aide de l’IA

Connexe cAdvisor Vulnérabilités :

CVE ID

Gravité

Partition

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-116591HIGH8.7
  • cAdvisor logocAdvisor
  • knative-serving-fips-1.23
NonOuiOct 26, 2026
CVE-2026-97032HIGH7.5
  • Go logoGo
  • grafana-pyroscope-fips-2.2
NonOuiOct 08, 2026
CVE-2026-97031HIGH7.5
  • Go logoGo
  • argo-workflows-4.1
NonOuiOct 08, 2026
CVE-2026-85747MEDIUM6.8
  • cAdvisor logocAdvisor
  • fluxcd-source-controller-fips
NonOuiOct 13, 2026
CVE-2026-128085MEDIUM5.3
  • cAdvisor logocAdvisor
  • crossplane-provider-aws-imagebuilder-fips
NonOuiNov 13, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.

Évaluation de la demande

Ressources Wiz supplémentaires

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités