CVE-2025-30156

HIGHPre-NVD 8.98.9—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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 week
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.9Exploit: None knownExposed: 0

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.9(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity89% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 27, 2026

Last Modified

September 8, 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 Patch Available

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

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
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 rangeFixed inDependents
ceph16.2.11+ds-2 ... 20.2.4+ds-1 (63 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ceph18.2.7+ds-1 ... 20.2.4+ds-1 (20 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ceph18.2.7+ds-1 ... 20.2.2+ds-9 (18 versions)20.2.4+ds-1—

Weakness Classification(1)

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

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 24× in last 7d / 64× 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.

  1. 2026-09-19 20:57 UTCVendor advisory
  2. 2026-09-19 10:01 UTCVendor advisory
  3. 2026-09-18 22:46 UTCVendor advisory
  4. 2026-09-18 11:52 UTCVendor advisory
  5. 2026-09-18 00:58 UTCEG score recompute
  6. 2026-09-18 00:58 UTCVendor advisory
  7. 2026-09-17 14:04 UTCVendor advisory
  8. 2026-09-17 03:10 UTCVendor advisory
  9. 2026-09-16 15:39 UTCEG score recompute
  10. 2026-09-16 15:39 UTCVendor advisory
  11. 2026-09-16 14:07 UTCEPSS rescore
  12. 2026-09-16 05:13 UTCEPSS rescore
  13. 2026-09-16 04:33 UTCVendor advisory
  14. 2026-09-15 17:30 UTCVendor advisory
  15. 2026-09-15 06:35 UTCEG score recompute
  16. 2026-09-15 06:35 UTCVendor advisory
  17. 2026-09-14 19:40 UTCVendor advisory
  18. 2026-09-14 08:45 UTCVendor advisory
  19. 2026-09-13 21:51 UTCEG score recompute
  20. 2026-09-13 21:51 UTCVendor advisory
  21. 2026-09-13 16:46 UTCEPSS rescore
  22. 2026-09-13 10:57 UTCVendor advisory
  23. 2026-09-13 00:02 UTCEG score recompute
  24. 2026-09-13 00:02 UTCVendor advisory
  25. 2026-09-12 15:00 UTCEPSS rescore
Show 39 more
  1. 2026-09-12 13:08 UTCVendor advisory
  2. 2026-09-12 02:14 UTCVendor advisory
  3. 2026-09-11 15:19 UTCEG score recompute
  4. 2026-09-11 15:19 UTCVendor advisory
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:35 UTCEPSS rescore
  7. 2026-09-10 17:31 UTCEG score recompute
  8. 2026-09-10 09:33 UTCEPSS rescore
  9. 2026-09-09 19:43 UTCVendor advisory
  10. 2026-09-09 08:49 UTCEG score recompute
  11. 2026-09-09 08:49 UTCVendor advisory
  12. 2026-09-08 21:59 UTCEPSS rescore
  13. 2026-09-08 21:55 UTCVendor advisory
  14. 2026-09-08 13:16 UTCVendor advisory
  15. 2026-09-08 02:00 UTCEG score recompute
  16. 2026-09-08 02:00 UTCVendor advisory
  17. 2026-09-07 16:00 UTCEPSS rescore
  18. 2026-09-07 15:05 UTCVendor advisory
  19. 2026-09-06 16:14 UTCEG score recompute
  20. 2026-09-06 13:46 UTCEPSS rescore
  21. 2026-09-06 13:46 UTCEPSS rescore
  22. 2026-09-05 18:24 UTCEG score recompute
  23. 2026-09-04 09:40 UTCEG score recompute
  24. 2026-09-04 05:05 UTCEPSS rescore
  25. 2026-09-03 00:48 UTCEG score recompute
  26. 2026-09-02 14:11 UTCEPSS rescore
  27. 2026-09-01 15:36 UTCEG score recompute
  28. 2026-09-01 13:53 UTCEPSS rescore
  29. 2026-09-01 04:39 UTCEG score recompute
  30. 2026-09-01 04:04 UTCEG score recompute
  31. 2026-08-31 19:32 UTCEG score recompute
  32. 2026-08-31 18:34 UTCEG score recompute
  33. 2026-08-30 08:40 UTCEG score recompute
  34. 2026-08-30 01:21 UTCEPSS rescore
  35. 2026-08-28 23:53 UTCEG score recompute
  36. 2026-08-28 21:40 UTCEPSS rescore
  37. 2026-08-28 00:31 UTCEG score recompute
  38. 2026-08-27 23:23 UTCEG score recompute
  39. 2026-08-27 23:22 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-30156?
CVE-2025-30156 is a high vulnerability 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 CVE-2025-30156 disclosed?
CVE-2025-30156 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-30156 actively exploited?
CVE-2025-30156 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 99.4% of all scored CVEs.
What is the CVSS score of CVE-2025-30156?
CVE-2025-30156 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2025-30156?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-30156, 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-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.

Start Free Scan →Browse All CVEs