CVE-2026-6726 is a vulnerability in TPM 2.0 credential issuance logic that allows a local attacker with elevated privileges to inject falsified Attestation Keys or DevID Keys into a TPM-aware Certificate Authority pipeline. The forged credentials will then pass validation on downstream systems that rely on TPM attestations — systems that have no visibility into the compromise that minted them.
The CVSS 7.9 score reflects the technical severity of the vulnerability itself: local access with elevated privileges required, on a single system. That scoring is technically accurate but architecturally misleading. Once forged, the credential propagates through automated compliance verification, supply chain attestation logs, and zero-trust enforcement points on remote systems that never knew this vulnerability existed. The prerequisite constrains how an attacker enters the trust chain, but it does not constrain where the poisoned output goes. A forged AK minted on one system can travel across your entire attestation infrastructure.
The deeper problem is that downstream validation is often shallow. Most systems accepting TPM attestations verify the signature but do not fully validate the credential chain back to the legitimate issuance authority. If your attestation verification is trusting the signature without tracing the full lineage, you are relying on forged trust anchors without knowing it. Audit your attestation verification logic and confirm it validates the complete credential chain, not just the cryptographic signature.
This vulnerability class has appeared in prior TCG reference code cycles. The recurrence pattern suggests that credential issuance flaws in reference implementations propagate into firmware and hypervisors that will not receive updates for years. If you have TPM-based systems deployed, check whether your TPM firmware and hypervisor have vendor advisories for this vulnerability class — and treat the absence of an advisory as a signal to investigate, not proof of safety.