Type confusion in github.com/docker/distribution
Published 29 Jul 2022 · Updated 7 Aug 2026
Is your project on an affected github.com/docker/distribution?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <2.8.0+incompatible
- Fixed in
- 2.8.0+incompatible
go get github.com/docker/distribution@v2.8.0+incompatibleDetails
Systems that rely on digest equivalence for image attestations may be vulnerable to type confusion.
A maliciously crafted OCI Container Image can cause registry clients to parse the same image in two different ways without modifying the image's digest, invalidating the common pattern of relying on container image digests for equivalence.
This problem has been addressed in newer versions by improving validation in manifest unmarshalling.
Is GO-2022-0379 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/docker/distribution, and gives you the command that fixes it.
More advisories for github.com/docker/distribution
- LowCVE-2026-85747Distribution: Client does not verify returned content against requested digest in github.com/distribution/distribution · 5 Nov 2026
- MediumCVE-2026-85747Distribution: Client `manifests.Get()` does not verify returned content against requested digest · 15 Oct 2026
- HighCVE-2023-2253distribution catalog API endpoint can lead to OOM via malicious user input · 11 May 2023
- HighCVE-2017-11468Docker Registry has Allocation of Resources Without Limits or Throttling · 13 May 2022
- LowCVE-2017-11468Uncontrolled resource allocation in github.com/docker/distribution · 14 Apr 2021
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.