Skip to main content
Report · GCP Compute Engine SecurityAbout CVE-2026-6726Published

GCP-2026-054

Source GCP Compute Engine Security

0
Authoritative record:CVE-2026-6726· High 7.9

Not known to be exploited · CVSS 7.9 High.

Data as of 26 Oct 2026, 22:13 UTC

CVSS 3.1 base score
7.9High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Trusted Computing GroupTPM2.0Affected
  • <=184
Fixed in–

AI-suggested

No customer action is required. Google will proactively update affected systems during standard and planned maintenance windows to address this vulnerability.

Description

A vulnerability (CVE-2026-6726, also known as TCGVRT0010) has been identified in the Trusted Computing Group's TPM 2.0 reference implementation code, affecting all published revisions of the code (v1.16, v1.38, v1.59, v1.83, v184). This flaw could allow a privileged local attacker to obtain credentials from a TPM-aware Certificate Authority for a falsified TPM key, enabling the creation of fraudulent TPM 2.0 attestations. Google will proactively update affected systems during standard maintenance windows, and no customer action is required.

References

Community reviews

Loading reviews…