Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Distribution: stale blob access resurrection via repo-scoped redis descriptor cache invalidation

CVE-2026-35172GHSA-f2g3-hh2r-cwgc

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/distribution/distribution

    Affected
    <= 2.8.3
    Fixed in
    no fixed version recorded

  • Go github.com/distribution/distribution/v3

    Affected
    < 3.1.0
    Fixed in
    3.1.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-35172: 0.47% estimated exploitation activity in the next 30 days; percentile 40.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

summary: 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. Severity HIGH justification: this is a repo-local authorization bypass after explicit delete, with concrete confidentiality impact and no requirement for write access after the delete event. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5). CWE-284. affected version - repository: https://github.com/distribution/distribution - commit: ab67ffa0bda3712991194841d0fde727464feeb9 - affected versions: \<= 3.0.x, \<= 2.8.x when redis blob descriptor cache and delete are both enabled - affected file: -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-f2g3-hh2r-cwgc

  2. Revision 1 · created ·

    Published from osv record GO-2026-4942

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35172

Advisory: Distribution: stale blob access resurrection via repo-scoped redis descriptor cache invalidation
IDs: CVE-2026-35172, GHSA-f2g3-hh2r-cwgc
Record: https://patchnext.com/advisories/cve-2026-35172 (revision 2, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/distribution/distribution/v3 3.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/distribution/distribution: affected <= 2.8.3
- Go github.com/distribution/distribution/v3: affected < 3.1.0; fixed in 3.1.0

## Suggested inspection (read-only)
- Go github.com/distribution/distribution: check the installed version with your package manager.
- Go github.com/distribution/distribution/v3: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/distribution/distribution, github.com/distribution/distribution/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-4942 (OSV record GO-2026-4942 lists affected ranges: Go github.com/distribution/distribution >=0; Go github.com/distribution/distribution/v3 >=0 <3.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-f2g3-hh2r-cwgc (GitHub-reviewed advisory GHSA-f2g3-hh2r-cwgc lists affected ranges: Go github.com/distribution/distribution/v3 >=0 =0 <=2.8.3)

Commands are suggestions: review each one before running it.

Loading voting…