CVE-2026-50152

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (16th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-67274 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the Monitor subscription handler fails to properly authorize access to the configuration-key store, allowing any CephX user with only  mon allow r capabilities to read the entire store by sending a single crafted MMonSubscribe message. The config-key store holds sensitive secrets including OSD LUKS disk-encryption passphrases and, on cephadm-managed clusters, the SSH private key that cephadm uses to reach every host in the cluster. Because that key grants root on every node under the default cephadm configuration, a low-privileged read-only account can escalate to full cluster and host compromise. This issue is fixed in versions 20.2.4 and 19.2.6

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
16th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

MON config-key store improper authorization · Advisory · ceph/ceph · GitHub

https://github.com/ceph/ceph/security/advisories/GHSA-rg9p-5xcp-wm8h
GitHub commit

commit f2840d2fd338 (ceph/ceph)

Fix landed in ceph/ceph commit f2840d2fd338 — awaiting tagged release

https://github.com/ceph/ceph/commit/f2840d2fd338ab5de2865f0f78684bbf7b888c84
GitHub commit

commit d971bb2b6199 (ceph/ceph)

Fix landed in ceph/ceph commit d971bb2b6199 — awaiting tagged release

https://github.com/ceph/ceph/commit/d971bb2b6199f70b1708a20a63fa944ee7a94727

Vendor Advisories for CVE-2026-50152(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhceph/rhceph-9-rhel10:17908435272026-10-21redhat
redhatrhceph/rhceph-7-rhel9:17914524772026-10-15redhat
redhatrhceph/rhceph-8-rhel9:17911769902026-10-08redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ceph16.2.11+ds-2 ... 20.2.4+ds-1 (63 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ceph18.2.7+ds-1 ... 20.2.4+ds-1 (20 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ceph18.2.7+ds-1 ... 20.2.2+ds-9 (18 versions)
  • every version up to 20.2.4+ds-1: fixed in 20.2.4+ds-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 61× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 192 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 92 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-50152?
CVE-2026-50152 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the Monitor subscription handler fails to properly authorize access to the configuration-key store, allowing any CephX user with only mon allow r capabilities to…
When was the CVE record for CVE-2026-50152 published?
The CVE record for CVE-2026-50152 was published on August 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-50152 actively exploited?
CVE-2026-50152 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50152?
CVE-2026-50152 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50152?
A fix for CVE-2026-50152 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50152 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50152?

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

Book a Demo →Browse All CVEs