🛡️ CVE-2026-68823 — azure-confidential-ledger

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs administrative privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: High — administrative rights are needed first.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Changed — a successful attack reaches components beyond the vulnerable one.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-68823 is classified as CWE-749: Exposed Dangerous Method or Function. A powerful method is reachable by callers who should not be able to invoke it.

Affected software

CVE-2026-68823 is recorded against 1 package.

• azure-confidential-ledger

Timeline and source

Published on 7 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

msrc.microsoft.com

Other advisories for this package

azure-confidential-ledger has other advisories on record. If you are patching this one, these are worth checking on the same host:

• MAL-2022-1307 (published 20 Jun 2022)

Same weakness in other software

These advisories are the same class of weakness (CWE-749: Exposed Dangerous Method or Function) in other software:

• CVE-2026-18901 (7.2 High, published 5 Aug 2026)
• CVE-2026-20467 (6.0 Medium, published 3 Aug 2026)
• CVE-2026-54753 (5.9 Medium, published 31 Jul 2026)
• CVE-2026-44107 (7.5 High, published 30 Jul 2026)
• CVE-2026-41283 (9.5 Critical, published 23 Jul 2026)
• CVE-2026-45805 (8.8 High, published 15 Jul 2026)
• CVE-2026-53633 (9.8 Critical, published 14 Jul 2026)
• CVE-2025-53827 (9.1 Critical, published 6 Jul 2026)

Details

Affected Packages

References