CVE-2026-68155

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH 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 — 3 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: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(high)
EG Risk
39(Track)
EG Risk 39/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
No patch confirmed yet.
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(2)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 52× 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-08-21 02:12 UTCEG score recompute
  2. 2026-08-21 02:12 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 15:17 UTCGHSA enrichment
  5. 2026-08-20 04:21 UTCGHSA enrichment
  6. 2026-08-19 17:25 UTCEG score recompute
  7. 2026-08-19 17:25 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:55 UTCEG score recompute
  10. 2026-08-19 16:55 UTCGHSA enrichment
  11. 2026-08-19 16:19 UTCGHSA enrichment
  12. 2026-08-19 05:20 UTCGHSA enrichment
  13. 2026-08-18 18:21 UTCEG score recompute
  14. 2026-08-18 18:21 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 07:26 UTCEG score recompute
  17. 2026-08-18 07:26 UTCGHSA enrichment
  18. 2026-08-18 07:03 UTCEG score recompute
  19. 2026-08-18 07:03 UTCGHSA enrichment
  20. 2026-08-18 03:30 UTCGHSA enrichment
  21. 2026-08-17 16:35 UTCEG score recompute
  22. 2026-08-17 16:35 UTCGHSA enrichment
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 05:40 UTCEG score recompute
  25. 2026-08-17 05:40 UTCGHSA enrichment
Show 27 more
  1. 2026-08-17 05:11 UTCEG score recompute
  2. 2026-08-17 05:11 UTCGHSA enrichment
  3. 2026-08-17 03:54 UTCGHSA enrichment
  4. 2026-08-16 16:59 UTCEG score recompute
  5. 2026-08-16 16:59 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 06:04 UTCEG score recompute
  8. 2026-08-16 06:04 UTCGHSA enrichment
  9. 2026-08-15 19:10 UTCGHSA enrichment
  10. 2026-08-15 08:15 UTCEG score recompute
  11. 2026-08-15 08:15 UTCGHSA enrichment
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 21:20 UTCGHSA enrichment
  14. 2026-08-14 10:24 UTCEG score recompute
  15. 2026-08-14 10:24 UTCGHSA enrichment
  16. 2026-08-13 23:30 UTCEG score recompute
  17. 2026-08-13 23:30 UTCGHSA enrichment
  18. 2026-08-13 22:45 UTCEG score recompute▲ 7.50
  19. 2026-08-13 22:45 UTCGHSA enrichment
  20. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 06:59 UTCEG score recompute
  23. 2026-08-13 06:59 UTCGHSA enrichment
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-10 13:24 UTCNVD update
  26. 2026-08-10 12:21 UTCEG score recompute
  27. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

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 in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 50.7% of all scored CVEs.
What is the CVSS score of CVE-2026-68155?
CVE-2026-68155 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-68155?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68155, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs