CVE-2026-68155

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
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.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

libceph: Reject monmaps advertising zero monitors

A message of type CEPH_MSG_MON_MAP contains a monmap that is sent from a monitor to the client. This monmap contains information about the existing monitors in the cluster. Currently, a monmap indicating that there are zero monitors in the cluster is treated as valid. However, it is impossible to have zero monitors in the cluster and still receive a valid monmap from a monitor. Therefore, such a monmap must be corrupted and should be treated as invalid. Furthermore, a monmap with a monitor count of zero can subsequently crash the client when attempting to open a session with a monitor in __open_session(). This happens because the "BUG_ON(monc->monmap->num_mon < 1)" assertion in pick_new_mon() is triggered.

This patch extends a check in ceph_monmap_decode() to also reject arriving mon_maps with num_mon == 0 rather than only with num_mon > CEPH_MAX_MON.

[ idryomov: drop "log output for unusual values of num_mon" part ]

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

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%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

October 3, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
Patch available.
generic

libceph: Reject monmaps advertising zero monitors - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e67e8b694872c9bc66996040f9de9242f6236ed9
generic

libceph: Reject monmaps advertising zero monitors - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cd0d41bc569632eaaeccde9d2a6bc919ec00c407
generic

libceph: Reject monmaps advertising zero monitors - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40480eee361ed9676b3f844d532ac28b47251634
generic

libceph: Reject monmaps advertising zero monitors - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b249546f59c3d6d3592c10657f82bc3f1faa07c
generic

libceph: Reject monmaps advertising zero monitors - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0591a15815b498be628a937146e44487d599ba33

Vendor Advisories for CVE-2026-68155(6)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-rt-0:4.18.0-553.169.1.rt7.510.el8_102026-09-28redhat
redhatkernel-0:4.18.0-553.169.1.el8_102026-09-28redhat
redhatkernel-0:5.14.0-687.50.1.el9_82026-09-23redhat
redhatkernel-0:6.12.0-211.58.1.el10_22026-09-23redhat

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

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Data Freshness Timeline

(refreshed 30× in last 7d / 106× 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 210 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-68155?
CVE-2026-68155 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: libceph: Reject monmaps advertising zero monitors A message of type CEPHMSGMON_MAP contains a monmap that is sent from a monitor to the client. This monmap contains information about the existing monitors in the cluster. Currently,…
When was CVE-2026-68155 disclosed?
CVE-2026-68155 was first published on August 10, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68155 actively exploited?
CVE-2026-68155 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68155?
CVE-2026-68155 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68155?
A fix for CVE-2026-68155 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68155 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-68155

Explore →

Is Your Infrastructure Affected by CVE-2026-68155?

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

Book a Demo →Browse All CVEs