CVE-2025-30156

HIGHPre-NVD 8.98.9
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd 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
Trending — 3 sources updated this week

Also known asEUVD-2025-210807 (ENISA EUVD)Source: ENISA EUVD

8.9EG
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.1%CVSS: 8.9Exploit: 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 CephX authentication protocol encrypts tickets with AES-128-CBC in an unauthenticated mode that uses a hard-coded initialization vector and no message authentication, allowing an attacker to forge credentials and gain cluster-wide access. Because the ciphertext is malleable and the monitor will encrypt attacker-chosen entity names, an attacker holding one low-privilege key and able to observe CephX traffic can use the monitor as an encryption oracle and splice ciphertext blocks into valid tickets for privileged entities such as Manager, MDS, and OSD. The same lack of authentication also lets an attacker with CephX permissions escalate privileges by flipping a single bit in a service ticket to set its allow_all field to true. This issue is fixed in versions 20.2.4 and 19.2.6.

CVSS v3
8.9
EG Score
8.9HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity89% × 45%
Impact severity (EG Severity): CVSS 8.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
2nd
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 (8.9): severity, escalated by confirmed exploitation. This CVE's 8.9 is its impact severity (EG Severity), not escalated.

EG Severity
8.9 HIGHCVSS-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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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

October 19, 2026

Advisory Details (3)

Auto-updated Aug 27, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit 3078188a7bdd (ceph/ceph)

Fix landed in ceph/ceph commit 3078188a7bdd — awaiting tagged release

https://github.com/ceph/ceph/commit/3078188a7bdd89e2975280f2a906c71c2f6effd6
GitHub commit

commit 2ba086255de0 (ceph/ceph)

Fix landed in ceph/ceph commit 2ba086255de0 — awaiting tagged release

https://github.com/ceph/ceph/commit/2ba086255de09c8b95177717cc7e9dd4377e2f0f
GitHub advisoryMentions a patch (unverified)

AES-CBC misuse in CephX facilitating authentication bypass · Advisory · ceph/ceph · GitHub

https://github.com/ceph/ceph/security/advisories/GHSA-7q3q-3975-qw3q

Vendor Advisories for CVE-2025-30156(10)

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

Patch Availability(9)

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
redhatceph-2:19.2.1-423.el9cp2026-10-08redhat
redhatkernel-0:5.14.0-427.132.1.el9_42026-06-22redhat
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
redhatkernel-0:6.12.0-55.82.1.el10_02026-06-22redhat
redhatkernel-0:6.12.0-211.7.1.el10_22026-05-19redhat
redhatkernel-0:5.14.0-687.5.1.el9_82026-05-19redhat

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 9× in last 7d / 53× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 99 of 160 refreshes 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 61 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2025-30156?
CVE-2025-30156 is a high-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 CephX authentication protocol encrypts tickets with AES-128-CBC in an unauthenticated mode that uses a hard-coded initialization vector and no message…
When was the CVE record for CVE-2025-30156 published?
The CVE record for CVE-2025-30156 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-30156 actively exploited?
CVE-2025-30156 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-30156?
CVE-2025-30156 has a CVSS base score of 8.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-30156?
A fix for CVE-2025-30156 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-30156 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-2025-30156

Explore →

Is Your Infrastructure Affected by CVE-2025-30156?

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

Book a Demo →Browse All CVEs