CVE-2026-35172

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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 v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

April 6, 2026

Last Modified

September 9, 2026

Advisory Details (8)

Auto-updated Jul 1, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35172.json
redhat

2455571 – (CVE-2026-35172) CVE-2026-35172 github.com/distribution/distribution: Distribution: Information disclosure via stale references after content deletion

https://bugzilla.redhat.com/show_bug.cgi?id=2455571
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-35172
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:26543
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:26529
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:25045
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:23234
github Patch Available🟡 PoC Available

Stale blob access resurrection via repo-scoped redis descriptor cache invalidation · Advisory · distribution/distribution · GitHub

https://github.com/distribution/distribution/security/advisories/GHSA-f2g3-hh2r-cwgc

Vendor Advisories for CVE-2026-35172(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhatopenshift4/ose-operator-lifecycle-manager:17818337952026-07-01redhat
redhatopenshift4/ose-operator-lifecycle-manager:17811227732026-06-25redhat
redhatopenshift4/ose-operator-lifecycle-manager:17811230522026-06-25redhat
redhatopenshift4/ose-operator-lifecycle-manager-rhel9:17809572682026-06-17redhat
redhatopenshift4/ose-operator-lifecycle-manager-rhel9:17799154992026-06-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/distribution/distribution———
github.com/distribution/distribution/v3—3.1.0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
docker-registry2.7.1+ds2-7 ... 2.8.3+ds1-3 (12 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
docker-registry2.8.2+ds1-1, 2.8.3+ds1-1, 2.8.3+ds1-2, 2.8.3+ds1-3——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
docker-registry2.8.3+ds1-2, 2.8.3+ds1-3——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
docker-registry2.8.3+ds1-22.8.3+ds1-3—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 195 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-09 13:42 UTCEG score recompute
  8. 2026-09-09 13:42 UTCVendor advisory
  9. 2026-09-09 12:40 UTCEG score recompute
  10. 2026-09-09 12:40 UTCVendor advisory
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 13:29 UTCEG score recompute
  15. 2026-09-04 13:29 UTCVendor advisory
  16. 2026-09-04 12:23 UTCEG score recompute
  17. 2026-09-04 12:23 UTCVendor advisory
  18. 2026-09-04 05:06 UTCEPSS rescore
  19. 2026-09-03 23:16 UTCOSV refresh
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 13:53 UTCEPSS rescore
  22. 2026-09-01 04:39 UTCEPSS rescore
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-28 21:41 UTCEPSS rescore
Show 75 more
  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 12:21 UTCEG score recompute
  11. 2026-08-17 12:21 UTCVendor advisory
  12. 2026-08-17 12:13 UTCEG score recompute
  13. 2026-08-17 12:13 UTCVendor advisory
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 08:22 UTCEG score recompute
  16. 2026-08-16 08:22 UTCVendor advisory
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 18:45 UTCVendor advisory
  20. 2026-08-14 05:31 UTCEG score recompute
  21. 2026-08-14 05:31 UTCVendor advisory
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 09:43 UTCVendor advisory
  24. 2026-08-12 19:44 UTCEG score recompute
  25. 2026-08-12 19:44 UTCVendor advisory
  26. 2026-08-12 13:50 UTCEPSS rescore
  27. 2026-08-12 00:49 UTCEG score recompute
  28. 2026-08-12 00:49 UTCVendor advisory
  29. 2026-08-11 13:24 UTCEG score recompute
  30. 2026-08-11 13:24 UTCVendor advisory
  31. 2026-08-11 12:24 UTCEG score recompute
  32. 2026-08-11 12:24 UTCVendor advisory
  33. 2026-08-11 03:17 UTCEG score recompute
  34. 2026-08-11 03:17 UTCVendor advisory
  35. 2026-08-11 00:00 UTCEPSS rescore
  36. 2026-08-10 03:52 UTCVendor advisory
  37. 2026-08-09 16:26 UTCEG score recompute
  38. 2026-08-09 16:26 UTCVendor advisory
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 05:01 UTCEG score recompute
  41. 2026-08-09 05:01 UTCVendor advisory
  42. 2026-08-08 16:37 UTCEPSS rescore
  43. 2026-08-08 02:28 UTCEG score recompute
  44. 2026-08-08 02:28 UTCVendor advisory
  45. 2026-08-07 15:03 UTCEG score recompute
  46. 2026-08-07 15:03 UTCVendor advisory
  47. 2026-08-06 13:46 UTCEPSS rescore
  48. 2026-08-06 13:01 UTCVendor advisory
  49. 2026-08-06 00:06 UTCEG score recompute
  50. 2026-08-06 00:06 UTCVendor advisory
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:38 UTCEPSS rescore
  54. 2026-08-03 22:27 UTCEG score recompute
  55. 2026-08-03 22:27 UTCVendor advisory
  56. 2026-08-03 10:36 UTCEPSS rescore
  57. 2026-08-03 01:50 UTCVendor advisory
  58. 2026-08-02 14:22 UTCEG score recompute
  59. 2026-08-02 14:22 UTCVendor advisory
  60. 2026-08-02 02:27 UTCEPSS rescore
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-30 16:28 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-27 14:13 UTCEPSS rescore
  65. 2026-07-26 09:05 UTCEG score recompute
  66. 2026-07-26 09:05 UTCVendor advisory
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-25 14:18 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-24 14:17 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 03:10 UTCEG score recompute
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-21 15:24 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-35172?
CVE-2026-35172 is a high vulnerability published on April 6, 2026. 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…
When was CVE-2026-35172 disclosed?
CVE-2026-35172 was first published in the National Vulnerability Database on April 6, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35172 actively exploited?
CVE-2026-35172 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.7% of all scored CVEs.
What is the CVSS score of CVE-2026-35172?
CVE-2026-35172 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-35172?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35172, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-35172

Explore →

Is Your Infrastructure Affected by CVE-2026-35172?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs