Distribution has stale blob access resurrection via repo-scoped redis descriptor cache invalidation
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-35172US | — | — | ||
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.… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:23234WEB
- https://access.redhat.com/errata/RHSA-2026:25045WEB
- https://access.redhat.com/errata/RHSA-2026:26529WEB
- https://access.redhat.com/errata/RHSA-2026:26543WEB
- https://access.redhat.com/errata/RHSA-2026:28893WEB
- https://access.redhat.com/errata/RHSA-2026:37387WEB
- https://access.redhat.com/security/cve/CVE-2026-35172WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2455571WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan