CVE-2026-68823

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-07. the CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
9.1EG
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.1Exploit: None knownExposed: 0

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

Exposed dangerous method or function in Azure Confidential Ledger allows an authorized attacker to execute code over a network.

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

Published

August 6, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68823

Vendor Advisories for CVE-2026-68823(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-68823?
CVE-2026-68823 is a critical vulnerability published on August 6, 2026. Exposed dangerous method or function in Azure Confidential Ledger allows an authorized attacker to execute code over a network.
When was CVE-2026-68823 disclosed?
CVE-2026-68823 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68823 actively exploited?
CVE-2026-68823 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 59.2% of all scored CVEs.
What is the CVSS score of CVE-2026-68823?
CVE-2026-68823 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-68823?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68823, 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-68823

Explore →

Is Your Infrastructure Affected by CVE-2026-68823?

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

Start Free Scan →Browse All CVEs