Quick answers
- Is CVE-2026-6726 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6726 being exploited in the wild.
- How severe is CVE-2026-6726?
- High severity, with a CVSS score of 7.9, published 11 August 2026.
- Which products and versions are affected?
- Trusted Computing Group TPM 2.0 Reference Implementation v1.16, v1.38, v1.59, v1.83, v1.84.
- Is there a fix for CVE-2026-6726?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-6726 attacked?
- It is attacked with local access or from the adjacent network, in device firmware.
- Am I affected by CVE-2026-6726?
- Check whether you run Google Cloud Platform or Trusted Computing Group TPM 2.0 Reference Implementation at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
CVE-2026-6726 (also designated TCGVRT0010) is a vulnerability affecting the Trusted Computing Group's TPM 2.0 reference implementation across all published code revisions. TPM 2.0 is a hardware security module specification responsible for protecting cryptographic keys, secure boot verification, and platform authentication. The exact vulnerability class and attack vector are not disclosed in the advisory, but the firmware-level nature suggests potential memory corruption or cryptographic weakness. Exploitation would require local or adjacent network access to the TPM interface. Google is addressing this via proactive patching during scheduled maintenance windows without requiring customer intervention.
Affected products
- Trusted Computing Group TPM 2.0 Reference Implementation v1.16, v1.38, v1.59, v1.83, v1.84
Timeline
- 2026-08-11: disclosed