CVE-2026-68823

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM 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(medium)
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
48%
KEV
Not listed

Published

August 6, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 15, 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 76× in last 7d / 350× 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 574 total refreshes for this CVE.

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

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 September 16, 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 52.4% 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.