Access Control Bypass Affecting github.com/distribution/distribution/v3/registry/storage/cache/redis package, versions <3.1.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Access Control Bypass vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMDISTRIBUTIONDISTRIBUTIONV3REGISTRYSTORAGECACHEREDIS-15922295
- published7 Apr 2026
- disclosed6 Apr 2026
- creditOleh Konko
Introduced: 6 Apr 2026
CVE-2026-35172 Â (opens in a new tab)How to fix?
Upgrade github.com/distribution/distribution/v3/registry/storage/cache/redis to version 3.1.0 or higher.
Overview
Affected versions of this package are vulnerable to Access Control Bypass due to the possibility to restore read access in repo a after an explicit delete when both storage.cache.blobdescriptor: redis and storage.delete.enabled: true are enabled. An attacker can regain unauthorized read access to previously deleted blobs by triggering a Stat or Get operation from a different repository, which repopulates the shared descriptor and restores access in the original repository.
Note:
This is only exploitable if both storage.cache.blobdescriptor: redis and storage.delete.enabled: true are enabled.