# CVE-2026-35172: Distribution has stale blob access resurrection via repo-scoped redis descriptor cache invalidation

> Attackers can regain read access to deleted blobs in one repository by exploiting stale cache entries in another, requiring specific Redis and delete configurations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 9 Sep 2026
- **Also known as:** BIT-distribution-2026-35172, CLEANSTART-2026-HS45258, CLEANSTART-2026-TN85120, DEBIAN-CVE-2026-35172, GHSA-f2g3-hh2r-cwgc, GO-2026-4942, MINI-2p7v-3hgm-ppx2, MINI-3hg3-4mfx-6v29, MINI-57xw-f345-cq8f, MINI-58jc-wj8w-hp5v, MINI-5jx2-23p4-pmf3, MINI-6fpc-q42g-f8qg, MINI-6rpc-gjg8-c493, MINI-775w-vpvv-mv82, MINI-7vv7-9rwh-26jc, MINI-949m-hxch-x7c8, MINI-9j26-5p8c-99cr, MINI-c4g8-74p6-pv8x, MINI-frqf-gp8q-c2m4, MINI-hx2h-74jw-x39p, MINI-m92j-qv2x-473w, MINI-pjp9-vh8x-836h, MINI-pmcm-xg5m-v8v4, MINI-pvwp-648v-wh5w, MINI-q46g-8x58-mp6x, MINI-r75m-38hp-7vpp, MINI-rrr5-3fcm-2f9f, MINI-rrvx-hmjw-hmfc, MINI-x8vv-vp6c-m689, MINI-x9jw-vwgf-9945, MINI-xv64-hrm7-xj76, UBUNTU-CVE-2026-35172

## What is CVE-2026-35172?

CVE-2026-35172 is a high-severity missing authorization vulnerability in distribution, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.

Weakness: CWE-524 (Use of Cache Containing Sensitive Information), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-35172?

7 open source packages ship an affected version, including github.com/distribution/distribution, distribution and github.com/distribution/distribution/v3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/distribution/distribution` | Go | All versions | None |
| `github.com/distribution/distribution` | Go | All versions to 2.8.3 | None |
| `github.com/distribution/distribution` | Go | All versions to 2.8.3 | None |
| `distribution` | Bitnami | All versions | 3.1.0 |
| `github.com/distribution/distribution/v3` | Go | All versions | 3.1.0 |
| `github.com/distribution/distribution/v3` | Go | All versions | 3.1.0 |
| `github.com/distribution/distribution/v3` | Go | All versions | 3.1.0 |

Products: Distribution Distribution.

## How do I fix CVE-2026-35172?

Upgrade to a fixed version.

## Is CVE-2026-35172 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35172 exists.

## Other vulnerabilities in distribution

- [CVE-2026-41888](https://insights.sbomify.com/CVE-2026-41888/): Distribution: Tag deletion bypasses `storage.delete.enabled` configuration (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35172 and fix it if it is affected.

What it is: CVE-2026-35172 is a high-severity missing authorization vulnerability in distribution, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35172 exists.

Affected packages and fixed versions:
- github.com/distribution/distribution (Go): affected all versions; no fix listed
- github.com/distribution/distribution (Go): affected all versions up to 2.8.3; no fix listed
- github.com/distribution/distribution (Go): affected all versions up to 2.8.3; no fix listed
- distribution (Bitnami): affected all versions; fixed in 3.1.0
- github.com/distribution/distribution/v3 (Go): affected all versions; fixed in 3.1.0
- github.com/distribution/distribution/v3 (Go): affected all versions; fixed in 3.1.0
- github.com/distribution/distribution/v3 (Go): affected all versions; fixed in 3.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35172/ (Markdown: https://insights.sbomify.com/CVE-2026-35172/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35172
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35172
- OSV: https://osv.dev/vulnerability/CVE-2026-35172

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35172/
Summaries are generated and may contain mistakes; the official description above is the record.