Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-85747 medium CVSS 6.8

Vulnerability in github.com/docker/distribution (CVE-2026-85747)

Summary

Vulnerability in github.com/docker/distribution (CVE-2026-85747). Data can be tampered with by attackers. Exploitable via GET /v2/{name}/manifests/{digest}. Mitigation: upgrade to 3.1.2 or later.

Original description

The description as published by the source.

Summary

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 relying on digest pinning for supply-chain integrity — image policy controllers, mirrors, pull-through caches — is silently undermined. The bundled pull-through proxy (registry/proxy/proxymanifeststore.go) is itself an unguarded consumer and is directly exploitable.

Details

Root cause: registry/client/repository.go:488-505 reads the response body and passes it directly to distribution.UnmarshalManifest without ever computing digest.FromBytes(body) and comparing against the caller-supplied dgst. The Docker-Content-Digest response header is parsed (lines 251-292 in descriptorFromResponse) only to populate an out-parameter (ReturnContentDigest) 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 GET /v2/{name}/manifests/{digest} with:

  1. Docker-Content-Digest: (forged header)
  2. A…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-85747 has been found in github.com/docker/distribution.
Attackers can target a specific entry point like GET /v2/{name}/manifests/{digest} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.8/10.
What to do: upgrade github.com/docker/distribution to 3.1.2 or later.
If unsure, ask your IT team or search "github.com/docker/distribution CVE-2026-85747" on the vendor's site.

CVE-2026-85747 (github.com/docker/distribution) — CWE-354 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /v2/{name}/manifests/{digest} / distribution.UnmarshalManifest / dgst / descriptorFromResponse
Patched: 3.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-354) exists in github.com/docker/distribution. Attackers reach the vulnerable code path via GET /v2/{name}/manifests/{digest} without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/docker/distribution. Attack surface: GET /v2/{name}/manifests/{digest} / distribution.UnmarshalManifest / dgst / descriptorFromResponse.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 3.1.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /v2/{name}/manifests/{digest} requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/docker/distribution' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/docker/distribution' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/docker/distribution を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /v2/{name}/manifests/{digest}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /v2/{name}/manifests/{digest} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/docker/distribution to 3.1.2

    ステージング環境で 3.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /v2/{name}/manifests/{digest} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/docker/distribution
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"2.8.3"}]}]
go github.com/distribution/distribution/v3
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details