CVE-2026-68433

HIGHPre-NVD 8.68.6
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.6EG
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.6Exploit: 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: bound get_version reply decode to front len

handle_get_version_reply() uses msg->front_alloc_len as the decode boundary for MON_GET_VERSION_REPLY. That is the size of the reused reply buffer, not the number of bytes actually received.

A truncated reply can therefore pass ceph_decode_need() and decode the second u64 from stale tail bytes left in the buffer by an earlier message, causing an uninitialized memory read.

Use msg->front.iov_len as the receive-side decode boundary, matching other libceph reply handlers and limiting decoding to the bytes that were actually read from the wire.

CVSS v3
8.6
EG Score
8.6(high)
EG Risk
43(Track)
EG Risk 43/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
Severity86% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

libceph: bound get_version reply decode to front len - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: bound get_version reply decode to front len - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: bound get_version reply decode to front len - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: bound get_version reply decode to front len - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/340e0386aa39da181015bee38f309018c335ce16
generic

libceph: bound get_version reply decode to front len - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d934c934ec746d53fc7e4f53239792647bbae63

Vendor Advisories for CVE-2026-68433(1)

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

All Vendor Advisories

(1)

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 37× in last 7d / 47× 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 07:23 UTCEG score recompute
  2. 2026-08-21 07:23 UTCVendor advisory
  3. 2026-08-21 07:23 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 18:46 UTCGHSA enrichment
  6. 2026-08-20 06:10 UTCGHSA enrichment
  7. 2026-08-19 17:33 UTCEG score recompute
  8. 2026-08-19 17:33 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 16:47 UTCEG score recompute
  11. 2026-08-19 16:47 UTCGHSA enrichment
  12. 2026-08-19 09:06 UTCGHSA enrichment
  13. 2026-08-18 20:29 UTCEG score recompute
  14. 2026-08-18 20:29 UTCGHSA enrichment
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 07:53 UTCGHSA enrichment
  18. 2026-08-17 19:15 UTCEG score recompute
  19. 2026-08-17 19:15 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 06:31 UTCEG score recompute
  22. 2026-08-17 06:31 UTCGHSA enrichment
  23. 2026-08-17 05:35 UTCEG score recompute
  24. 2026-08-17 05:35 UTCGHSA enrichment
  25. 2026-08-17 03:24 UTCEG score recompute
Show 22 more
  1. 2026-08-17 03:24 UTCGHSA enrichment
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 14:47 UTCEG score recompute
  5. 2026-08-16 14:47 UTCGHSA enrichment
  6. 2026-08-16 02:11 UTCGHSA enrichment
  7. 2026-08-15 13:35 UTCEG score recompute
  8. 2026-08-15 13:35 UTCGHSA enrichment
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-15 00:58 UTCGHSA enrichment
  11. 2026-08-14 12:21 UTCEG score recompute
  12. 2026-08-14 12:21 UTCGHSA enrichment
  13. 2026-08-13 23:45 UTCEG score recompute
  14. 2026-08-13 23:45 UTCGHSA enrichment
  15. 2026-08-13 23:03 UTCEG score recompute 8.60
  16. 2026-08-13 23:03 UTCGHSA enrichment
  17. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 8.6 · severity → HIGH
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-12 00:19 UTCNVD update
  21. 2026-08-12 00:15 UTCEG score recompute
  22. 2026-08-12 00:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68433?
CVE-2026-68433 is a high vulnerability published on August 12, 2026. In the Linux kernel, the following vulnerability has been resolved: libceph: bound get_version reply decode to front len handlegetversionreply() uses msg->frontalloc_len as the decode boundary for MONGETVERSION_REPLY. That is the size of the reused reply buffer, not the number of bytes actually…
When was CVE-2026-68433 disclosed?
CVE-2026-68433 was first published in the National Vulnerability Database on August 12, 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-68433 actively exploited?
CVE-2026-68433 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 77.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68433?
CVE-2026-68433 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-68433?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68433, 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-68433

Explore →

Is Your Infrastructure Affected by CVE-2026-68433?

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