CVE-2026-68160

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: 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:

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()

ceph_handle_caps() reads snap_trace_len from the wire-format ceph_mds_caps header and uses it unconditionally to build a fake end pointer (snaptrace + snaptrace_len) that is later handed to ceph_update_snap_trace() in the CEPH_CAP_OP_IMPORT case:

snaptrace = h + 1; snaptrace_len = le32_to_cpu(h->snap_trace_len); p = snaptrace + snaptrace_len; ... case CEPH_CAP_OP_IMPORT: if (snaptrace_len) { ... if (ceph_update_snap_trace(mdsc, snaptrace, snaptrace + snaptrace_len, false, &realm)) { ... }

ceph_update_snap_trace() then decodes a struct ceph_mds_snap_realm from snaptrace using ceph_decode_need(&p, e, sizeof(*ri), bad) with the attacker-supplied fake end e == snaptrace + snaptrace_len. With snaptrace_len == 0xFFFFFFFF the bound check is trivially satisfied, ri = p reads sizeof(struct ceph_mds_snap_realm) past the legitimate msg->front buffer, and ri->num_snaps / ri->num_prior_parent_snaps then drive further out-of-bounds reads of the encoded snap arrays.

The eleven msg_version >= 2 .. msg_version >= 12 decoder blocks above the op switch each catch this OOB through their ceph_decode_*_safe() / ceph_decode_need() helpers, but they sit behind a hdr.version-gated if, so a malicious or compromised MDS that sets msg->hdr.version = 1 reaches the IMPORT path with no version-gated decoder having validated snap_trace_len. The shape has been present since ceph_handle_caps() was introduced.

Validate snap_trace_len against the message front buffer before consuming it, using the canonical ceph_decode_need() / ceph_has_room() helper. The helper bounds the length with subtraction (n <= end - p, guarded by end >= p) rather than pointer addition, so it is wrap-safe for the attacker-controlled u32 length on 32-bit builds where p + snap_trace_len could overflow the address space. This matches the rest of the ceph decode path (e.g. the pool_ns_len check a few lines below), and the existing goto bad cleanup already covers this exit path.

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

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (8)

Auto-updated Aug 19, 2026
No patch confirmed yet.
generic

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9081c71796724ffe96cba253f68fbe42363c5295
generic

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71893c342a26bcff92eaab0b2b75d64aed19308a
generic

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4dbc71bcaf9a30abf3920a4e2cc4ed33bba78c02
generic

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c011137194036424e974677e0f1592e22a33d8c
generic

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03b417afce19ee6b6e61f1bbbbebac924c9f36d1

Vendor Advisories for CVE-2026-68160(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 66× in last 7d / 81× 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 06:32 UTCVendor advisory
  2. 2026-08-21 06:32 UTCGHSA enrichment
  3. 2026-08-21 02:51 UTCVendor advisory
  4. 2026-08-21 02:51 UTCGHSA enrichment
  5. 2026-08-20 23:09 UTCEG score recompute
  6. 2026-08-20 23:09 UTCGHSA enrichment
  7. 2026-08-20 22:56 UTCEPSS rescore
  8. 2026-08-20 19:29 UTCGHSA enrichment
  9. 2026-08-20 15:48 UTCGHSA enrichment
  10. 2026-08-20 12:08 UTCGHSA enrichment
  11. 2026-08-20 08:27 UTCGHSA enrichment
  12. 2026-08-20 04:47 UTCGHSA enrichment
  13. 2026-08-20 01:06 UTCGHSA enrichment
  14. 2026-08-19 21:25 UTCGHSA enrichment
  15. 2026-08-19 17:25 UTCEG score recompute
  16. 2026-08-19 17:25 UTCGHSA enrichment
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-19 16:55 UTCEG score recompute
  19. 2026-08-19 16:55 UTCGHSA enrichment
  20. 2026-08-19 14:08 UTCGHSA enrichment
  21. 2026-08-19 10:27 UTCGHSA enrichment
  22. 2026-08-19 06:47 UTCGHSA enrichment
  23. 2026-08-19 02:58 UTCGHSA enrichment
  24. 2026-08-18 22:47 UTCGHSA enrichment
  25. 2026-08-18 18:59 UTCGHSA enrichment
Show 56 more
  1. 2026-08-18 15:18 UTCEG score recompute
  2. 2026-08-18 15:18 UTCGHSA enrichment
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-18 11:15 UTCGHSA enrichment
  5. 2026-08-18 07:27 UTCGHSA enrichment
  6. 2026-08-18 03:46 UTCGHSA enrichment
  7. 2026-08-18 00:05 UTCGHSA enrichment
  8. 2026-08-17 20:22 UTCGHSA enrichment
  9. 2026-08-17 16:41 UTCEG score recompute
  10. 2026-08-17 16:41 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 13:01 UTCGHSA enrichment
  13. 2026-08-17 09:20 UTCGHSA enrichment
  14. 2026-08-17 05:40 UTCEG score recompute
  15. 2026-08-17 05:40 UTCGHSA enrichment
  16. 2026-08-17 05:10 UTCEG score recompute
  17. 2026-08-17 05:10 UTCGHSA enrichment
  18. 2026-08-17 04:44 UTCGHSA enrichment
  19. 2026-08-17 01:03 UTCGHSA enrichment
  20. 2026-08-16 21:22 UTCGHSA enrichment
  21. 2026-08-16 17:41 UTCEG score recompute
  22. 2026-08-16 17:41 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:00 UTCGHSA enrichment
  25. 2026-08-16 10:19 UTCGHSA enrichment
  26. 2026-08-16 06:39 UTCGHSA enrichment
  27. 2026-08-16 02:59 UTCEG score recompute
  28. 2026-08-16 02:59 UTCGHSA enrichment
  29. 2026-08-15 23:19 UTCGHSA enrichment
  30. 2026-08-15 19:38 UTCGHSA enrichment
  31. 2026-08-15 15:57 UTCGHSA enrichment
  32. 2026-08-15 12:16 UTCGHSA enrichment
  33. 2026-08-15 08:35 UTCGHSA enrichment
  34. 2026-08-15 04:54 UTCEG score recompute
  35. 2026-08-15 04:54 UTCGHSA enrichment
  36. 2026-08-15 01:30 UTCEPSS rescore
  37. 2026-08-15 01:13 UTCGHSA enrichment
  38. 2026-08-14 21:33 UTCGHSA enrichment
  39. 2026-08-14 17:52 UTCGHSA enrichment
  40. 2026-08-14 14:12 UTCGHSA enrichment
  41. 2026-08-14 10:31 UTCGHSA enrichment
  42. 2026-08-14 06:51 UTCGHSA enrichment
  43. 2026-08-14 03:10 UTCEG score recompute
  44. 2026-08-14 03:10 UTCGHSA enrichment
  45. 2026-08-13 23:30 UTCEG score recompute
  46. 2026-08-13 23:30 UTCGHSA enrichment
  47. 2026-08-13 22:45 UTCEG score recompute 9.80
  48. 2026-08-13 22:45 UTCGHSA enrichment
  49. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  50. 2026-08-13 22:00 UTCEPSS rescore
  51. 2026-08-13 14:58 UTCEG score recompute
  52. 2026-08-13 14:58 UTCGHSA enrichment
  53. 2026-08-12 13:51 UTCEPSS rescore
  54. 2026-08-10 13:24 UTCNVD update
  55. 2026-08-10 12:21 UTCEG score recompute
  56. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68160?
CVE-2026-68160 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: ceph: fix pre-auth out-of-bounds read on snaptrace in cephhandlecaps() cephhandlecaps() reads snaptracelen from the wire-format cephmdscaps header and uses it unconditionally to build a fake end pointer (snaptrace + snaptrace_len)…
When was CVE-2026-68160 disclosed?
CVE-2026-68160 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-68160 actively exploited?
CVE-2026-68160 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 47.4% of all scored CVEs.
What is the CVSS score of CVE-2026-68160?
CVE-2026-68160 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68160, 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-68160

Explore →

Is Your Infrastructure Affected by CVE-2026-68160?

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