LiveActive security incident?Get immediate response
CVE Record

CVE-2026-35172: 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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can make container registry content readable again after it was explicitly deleted, but only under a specific Distribution configuration using Redis blob descriptor caching and enabled deletes. The business concern is confidentiality: deleted blobs may become accessible again, undermining cleanup, access-control expectations, or repository separation.

Executive priority

Prioritize remediation for internet-facing or multi-tenant registries, especially where deleted images may contain secrets, proprietary code, or regulated data. The issue is high severity but configuration-dependent, so confirm exposure before emergency response.

Technical view

Distribution before 3.1.0 leaves stale repo-scoped blob membership when deleting a blob with storage.cache.blobdescriptor set to redis and storage.delete.enabled true. A later Stat or Get from another repository can repopulate the shared digest descriptor, restoring read access in the original repository. CVSS 3.1 is 7.5, confidentiality impact high.

Likely exposure

Exposure is likely limited to container registries running distribution/distribution before 3.1.0 with Redis blobdescriptor cache enabled and storage deletes enabled. The source bundle does not show broader affected products beyond Distribution and Red Hat-tracked advisories.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. The attack surface is network-accessible registry behavior with no privileges required per CVSS, but the provided sources do not include public exploit details or real-world abuse evidence.

Researcher notes

The key condition is cache invalidation asymmetry: shared digest descriptors are cleared, while repo-scoped membership remains stale. Validation should focus on affected configuration, version, and post-delete read behavior. Avoid assuming impact where Redis blobdescriptor caching or delete support is absent.

Mitigation direction

  • Upgrade distribution/distribution to version 3.1.0 or later.
  • Apply applicable Red Hat errata fixes for packaged Distribution components.
  • Identify registries using Redis blobdescriptor cache with deletes enabled.
  • If upgrade is delayed, check vendor guidance for supported configuration workarounds.
  • Review deleted sensitive blobs that may have relied on deletion for access removal.

Validation and detection

  • Inventory Distribution versions across all container registry deployments.
  • Check configuration for storage.cache.blobdescriptor: redis.
  • Check configuration for storage.delete.enabled: true.
  • Confirm fixed vendor packages or Distribution 3.1.0 are deployed.
  • Test that deleted blobs remain inaccessible after cross-repository blob lookups.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-524: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-35172 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-35172Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPgithub.com/distribution/distribution: Distribution: Information disclosure via stale references after content deletion
other:Red Hat severity ratingcvssV3_1
  • 2026-04-06T20:01:47.396Z: Reported to Red Hat.
  • 2026-04-06T19:08:44.512Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
distributiondistribution< 3.1.0Listed
Weakness

CWE details

CWE-284CWE-524

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.