CVE-2026-35172
Distribution broken access control
- Published6 Apr 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:23234
- https://access.redhat.com/errata/RHSA-2026:25045
- https://access.redhat.com/errata/RHSA-2026:26529
- https://access.redhat.com/errata/RHSA-2026:26543
- https://access.redhat.com/errata/RHSA-2026:28893
- https://access.redhat.com/errata/RHSA-2026:37387
- https://access.redhat.com/security/cve/CVE-2026-35172
- https://bugzilla.redhat.com/show_bug.cgi?id=2455571
- https://github.com/distribution/distribution/security/advisories/GHSA-f2g3-hh2r-cwgc
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35172.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-35172 being actively exploited?
CVE-2026-35172 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.67%.
How severe is CVE-2026-35172?
CVE-2026-35172 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.67% probability of exploitation.
Which products are affected by CVE-2026-35172?
Affected products include Distribution.
How do I fix CVE-2026-35172?
Upgrade affected software to a fixed version, for example Distribution 3.1.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-35172 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.