An information leakage vulnerability was reported in the TCG TPM 2.0 reference code that could

CVE-2026-6726 is an object-slot-reuse flaw in the TCG TPM 2.0 reference implementation code. Due to improper type casting and failure to clear sensitive data from reused object slots (CWE-704, CWE-1266), a local attacker with privileged access to the TPM command interface can craft commands that cause the TPM to treat a falsified key as legitimate. The attacker can then present this falsified key — an Attestation Key, DevID key, or TLS authentication key — to a TPM-aware Certificate Authority and obtain a valid credential. This breaks the fundamental trust assertion that TPM-backed keys were genuinely generated inside tamper-resistant hardware. Affected hardware includes AMD fTPM across Ryzen 3000–9000 series and Ryzen AI families, Intel fTPM implementations, and Nuvoton NPCT7xx discrete TPMs with firmware prior to 7.2.4.1 / 7.2.5.0. The installed base is enormous — hundreds of millions of devices.

Despite the massive footprint, the attack requires local administrator or root-level access to the TPM command interface. This is a hard post-compromise prerequisite: the attacker must already own the box before they can abuse the TPM. The blast radius is confined to the compromised host's identity — forging that machine's attestation, not impersonating other machines. Some sources cite a vendor CVSS of 8.5 (HIGH), but no authoritative NVD or MITRE score has been published. The HIGH label overweights the theoretical impact of undermining hardware root-of-trust while underweighting the fact that an attacker with local admin already controls the host. In environments not using TPM-based attestation, conditional access, or device identity certificates, this vulnerability has near-zero practical impact. For organizations relying on Windows Hello for Business, Intune device compliance, or zero-trust device attestation, the residual risk is real but incremental — the attacker is extending an existing compromise, not initiating one.

Why this verdict

• Privileged local access required: The attacker must already hold admin/root on the target host. This is a post-compromise prerequisite that eliminates all remote attack scenarios and means an independent, full attack chain must succeed before CVE-2026-6726 becomes relevant. Downward pressure: significant.
• No public PoC or weaponized tooling: Exploitation requires intimate knowledge of TPM 2.0 command internals and slot management. No researcher has published exploit code. The bar for weaponization is high. Downward pressure: moderate.
• Per-host blast radius: The forgery applies to the compromised host's TPM only. The attacker cannot impersonate other devices or achieve lateral movement through this flaw alone. Impact is identity persistence on a single already-compromised endpoint. Downward pressure: significant.
• Role multiplier: (a) *Low-value role (workstation/dev sandbox)*: chain succeeds but impact is trivial — attacker already owns the box and gains only attestation persistence. Blast radius: host-only. (b) *Typical role (enterprise endpoint with Intune/WHfB)*: chain succeeds and attacker gains conditional-access bypass persistence on that single device. Blast radius: host → tenant-edge (one device's compliance posture). (c) *High-value role (TPM-aware CA server, HSM host, confidential-computing node)*: chain could succeed if the server runs vulnerable firmware, but these roles represent <1% of the TPM installed base (most TPMs are in endpoints, not servers running CA services). Even in this role, impact is identity forgery for that one server, not domain/fleet compromise. No high-value-role outcome reaches the domain-takeover or fleet-compromise threshold needed to trigger the HIGH floor.
• Enormous installed base is offset by attack locality: Hundreds of millions of devices carry vulnerable firmware, but the vulnerability has zero remote attack surface. The population-at-risk is not 'all devices with TPMs' but 'all devices where an attacker has already achieved local admin AND the org relies on TPM attestation.' This is a small fraction of deployments.

Why not higher?

To warrant HIGH, the vulnerability would need either a remote attack vector, a path to fleet-scale impact, or active exploitation. CVE-2026-6726 has none of these. The local+privileged prerequisite means an attacker has already won the host before this flaw matters. The forgery is per-host and cannot propagate. No PoC exists and EPSS is bottom-quartile. While the installed base is vast, the *reachable* population (local admin + TPM attestation reliance) is narrow.

Why not lower?

Dropping to LOW would undervalue the real-world impact in organizations that have invested in TPM-based zero-trust architectures (Windows Hello for Business, Intune device compliance, 802.1X DevID). In those environments, forging TPM attestation undermines a deliberate security control and provides meaningful persistence. The flaw is also in a foundational security primitive (hardware root of trust), and the CWE combination (type confusion + data reuse) suggests a design-level weakness in the reference implementation that may have downstream implications beyond the currently documented attack.

1. Audit TPM firmware versions fleet-wide via MDM/UEM — Use Intune, SCCM, or your UEM platform to inventory TPM firmware versions across all managed endpoints. Identify hosts running pre-patch firmware. This is the foundation for a targeted remediation campaign. No mitigation SLA applies at MEDIUM — go straight to the 365-day remediation window.
2. Deploy OEM BIOS/firmware updates containing patched AGESA/TPM firmware — AMD, Intel, and Nuvoton have released fixes through OEM partners. Coordinate with ASUS, MSI, GIGABYTE, Lenovo, Dell, HP for BIOS updates. Prioritize hosts in environments using TPM-based attestation (WHfB, Intune compliance, 802.1X DevID). Apply within the 365-day noisgate remediation SLA.
3. Enable TPM command audit logging — On Windows, enable TPM diagnostics via Group Policy (Computer Configuration > Administrative Templates > System > Trusted Platform Module Services). On Linux, configure tpm2-abrmd logging. This provides detection coverage for anomalous TPM command sequences that could indicate exploitation attempts.
4. Layer conditional access beyond TPM attestation alone — Ensure conditional access policies do not rely solely on TPM attestation. Layer with user MFA, device compliance posture (OS patch level, EDR health), network location, and risk scoring. This limits the value of a forged TPM credential even if exploitation occurs.
5. Monitor CA audit logs for anomalous certificate issuance — If you operate a TPM-aware CA (e.g., ADCS with key attestation), review certificate issuance logs for unusual enrollment patterns. Flag certificates issued to devices with mismatched hardware identifiers or unexpected re-enrollment.

Run on each target Windows host as Administrator. Example: powershell -ExecutionPolicy Bypass -File .\Check-CVE-2026-6726.ps1. Requires admin privileges to query TPM firmware version. For Linux hosts with AMD fTPM, check BIOS/AGESA version instead.

# Check-CVE-2026-6726.ps1
# Checks TPM firmware version against known-vulnerable ranges for CVE-2026-6726
# Run as Administrator on target Windows host
# Exit codes: 1=VULNERABLE, 0=PATCHED, 2=UNKNOWN

$ErrorActionPreference = 'Stop'

try {
    $tpm = Get-TpmStatus -ErrorAction Stop
    if (-not $tpm.TpmPresent) {
        Write-Output "UNKNOWN - No TPM detected on this system"
        exit 2
    }

    $tpmInfo = Get-CimInstance -Namespace 'root\cimv2\Security\MicrosoftTpm' -ClassName 'Win32_Tpm' -ErrorAction Stop
    $manufacturer = $tpmInfo.ManufacturerIdTxt
    $fwVersion = $tpmInfo.ManufacturerVersion
    $specVersion = $tpmInfo.SpecVersion

    Write-Output "TPM Manufacturer: $manufacturer"
    Write-Output "Firmware Version: $fwVersion"
    Write-Output "Spec Version:     $specVersion"

    # Check if TPM 2.0
    if ($specVersion -notlike '2.0*') {
        Write-Output "UNKNOWN - TPM is not version 2.0; CVE-2026-6726 applies to TPM 2.0 only"
        exit 2
    }

    # Nuvoton NPCT7xx check
    if ($manufacturer -match 'NTC|Nuvoton') {
        # Vulnerable: < 7.2.4.1 or exactly 7.2.5.0
        # Fixed: >= 7.2.4.1 (in 7.2.4.x line) or >= 7.2.5.1
        if ($fwVersion -match '^7\.2\.5\.0$') {
            Write-Output "VULNERABLE - Nuvoton firmware $fwVersion is affected by CVE-2026-6726"
            exit 1
        }
        try {
            $parts = $fwVersion.Split('.') | ForEach-Object { [int]$_ }
            $ver = [version]$fwVersion
            $fixed = [version]'7.2.4.1'
            if ($ver -lt $fixed) {
                Write-Output "VULNERABLE - Nuvoton firmware $fwVersion is below fixed version 7.2.4.1"
                exit 1
            } else {
                Write-Output "PATCHED - Nuvoton firmware $fwVersion is at or above fixed version"
                exit 0
            }
        } catch {
            Write-Output "UNKNOWN - Could not parse Nuvoton firmware version: $fwVersion"
            exit 2
        }
    }

    # AMD fTPM check - rely on BIOS/AGESA version
    if ($manufacturer -match 'AMD') {
        Write-Output "UNKNOWN - AMD fTPM detected. Firmware is updated via BIOS/AGESA update."
        Write-Output "Check your OEM support site for BIOS updates addressing CVE-2026-6726."
        Write-Output "Current BIOS info:"
        $bios = Get-CimInstance -ClassName Win32_BIOS
        Write-Output "  BIOS Version: $($bios.SMBIOSBIOSVersion)"
        Write-Output "  BIOS Date:    $($bios.ReleaseDate)"
        exit 2
    }

    # Intel fTPM check
    if ($manufacturer -match 'INTC|Intel') {
        Write-Output "UNKNOWN - Intel fTPM detected. Check Intel SA advisory and OEM BIOS updates for CVE-2026-6726 fix status."
        Write-Output "Firmware version: $fwVersion"
        exit 2
    }

    # Other manufacturers
    Write-Output "UNKNOWN - Manufacturer '$manufacturer' not in known-affected list. Check vendor advisory."
    exit 2

} catch {
    Write-Output "UNKNOWN - Error querying TPM: $($_.Exception.Message)"
    exit 2
}

Sources

1. CERT/CC VU#431093 — TCG TPM 2.0 information leakage and timing side-channel advisory
2. Nuvoton SA-006 — Information leakage via falsified TPM keys
3. AMD Security Bulletin SB-7064 — TPM Reference Code Errata
4. Lenovo PS500722 — TPM 2.0 Reference Code Vulnerability (Firmware TPMs)
5. CISA ICS Advisory ICSA-26-111-01 — Siemens TPM 2.0
6. Quarkslab — Vulnerabilities in the TPM 2.0 reference implementation code
7. CISA Known Exploited Vulnerabilities Catalog