CVE-2026-6726: An information leakage vulnerability in the TCG TPM 2.0 reference code.

Published Aug 11, 2026
·
Updated

An information leakage vulnerability was reported in the TCG TPM 2.0 reference code that could allow a local attacker with elevated privileges to obtain a credential from a TPM-aware CA for a falsified TPM key (such as an Attestation Key, DevID Key or TLS authentication key) and falsify other TPM 2.0 attestations with this key. See also TCG VRT0010.

Other sources

CVE-2026-6726 is a Spoofing vulnerability in the TPM 2.0 reference implementation involving improper object-slot reuse. MITRE assigned this CVE on behalf of the Trusted Computing Group. This document incorporates updates to Microsoft Windows that address this vulnerability. Please see CVE-2026-6726 for more information.

Microsoft

MITRE: CVE-2026-6726 TPM 2.0 Improper Object Slot Reuse

Microsoft

Affected Software

24 affected componentsFixes available
Microsoft Windows 11=26H1
10.0.28000.2704
Microsoft Windows 11=23H2
10.0.22631.7517
Microsoft Windows 11=24H2
10.0.26100.916810.0.26100.9106
Microsoft Windows 11=23H2
10.0.22631.7517
Microsoft Windows 11=25H2
10.0.26200.916810.0.26100.9106
Microsoft Windows 10=1607
10.0.14393.9418
Microsoft Windows 10=1607
10.0.14393.9418
Microsoft Windows 11=24H2
10.0.26100.916810.0.26000.9106
Microsoft Windows 11=26H1
10.0.28000.2704
Microsoft Windows Server 2025<10.0.26100.33296, <10.0.26100.33222
10.0.26100.3329610.0.26100.33222
Microsoft Windows 11=25H2
10.0.26200.916810.0.26100.9106
Microsoft Windows 10=22H2
10.0.19045.7663
Microsoft Windows Server 2025<10.0.26100.33296, <10.0.26100.33222
10.0.26100.3329610.0.26100.33222
Microsoft Windows 10=22H2
10.0.19045.7663
Microsoft Windows 10=21H2
10.0.19044.7663
Microsoft Windows Server 2019<10.0.17763.9115
10.0.17763.9115
Microsoft Windows 10=22H2
10.0.19045.7663
Microsoft Windows 10=21H2
10.0.19044.7663
Microsoft Windows Server 2022<10.0.20348.5499, <10.0.20348.5440
10.0.20348.549910.0.20348.5440
Microsoft Windows 10=21H2
10.0.19044.7663
Microsoft Windows Server 2019<10.0.17763.9115
10.0.17763.9115
Microsoft Windows 10=1809
10.0.17763.9115
Microsoft Windows Server 2022<10.0.20348.5499, <10.0.20348.5440
10.0.20348.549910.0.20348.5440
Microsoft Windows 10=1809
10.0.17763.9115

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.2704Patch KB5121000
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.7517Patch KB5120240
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.9168Fixed in 10.0.26100.9106Patch KB5120994
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.9168Fixed in 10.0.26100.9106Patch KB5120994
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.9418Patch KB5120418
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.9168Fixed in 10.0.26000.9106Patch KB5120994
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.33296Fixed in 10.0.26100.33222Patch KB5120228
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.7663Patch KB5120249
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.7663Patch KB5120249
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.9115Patch KB5120238
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.5499Fixed in 10.0.20348.5440Patch KB5120229

Event History

Aug 11, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
CVE Published
via MITRE·03:24 PM
Data Sourced
via MITRE·03:24 PM
DescriptionWeakness
Data Sourced
via NVD·04:17 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-6726?

The severity of CVE-2026-6726 is rated as risk 44.

2

How do I fix CVE-2026-6726?

To fix CVE-2026-6726, it is recommended to apply the latest patches provided by the TCG TPM 2.0 reference code maintainers.

3

Who is affected by CVE-2026-6726?

CVE-2026-6726 affects users and systems utilizing the TCG TPM 2.0 reference code.

4

What kind of attack can exploit CVE-2026-6726?

CVE-2026-6726 can be exploited by a local attacker with elevated privileges to obtain credentials from a TPM-aware CA.

5

What types of keys can be compromised due to CVE-2026-6726?

CVE-2026-6726 could potentially compromise keys such as Attestation Key, DevID Key, or TLS authentication key.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203