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

Exp

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.

Published: 2026-04-06 Last update: 2026-04-27 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-35172 is rated Exploit Available (51.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-35172

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-35172

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-18 0.03% 0.06% +0.03%
2 2026-04-07 — 0.03% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-35172

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-35172

GitHub Security Advisory for CVE-2026-35172

GHSA-f2g3-hh2r-cwgc · Severity: high · Ecosystem: go — Distribution: stale blob access resurrection via repo-scoped redis descriptor cache invalidation

OS Trackers for CVE-2026-35172

vendor priority summary link
debian not yet assigned CVE-2026-35172 not yet assigned priority: Debian including 1 source packages (docker-registry), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2026-35172
redhat high — https://access.redhat.com/security/cve/CVE-2026-35172
suse high — https://www.suse.com/security/cve/CVE-2026-35172/
ubuntu medium CVE-2026-35172 medium priority: Ubuntu including 1 source packages (docker-registry), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 7. https://ubuntu.com/security/CVE-2026-35172

Affected software / configurations for CVE-2026-35172

Vendor Product Version Raw CPE
distribution distribution < 3.1.0 cpe:2.3:a:distribution:distribution:*:*:*:*:*:*:*:*

References for CVE-2026-35172

cvelogic Threat Intelligence