VU#431093: TCG TPM 2.0 reference code found vulnerable to information leakage and timing side-channel attacks
Source CERT/CC
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.9 High.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Trusted Computing GroupTPM2.0 | Affected
| Fixed in– |
AI-suggested
Multiple vendors have released firmware and software updates that incorporate fixes for these vulnerabilities. Users should install TPM firmware updates, operating system updates, or software patches provided by their platform or TPM vendor. Cloud providers using software TPM implementations may have deployed updates; customers should consult their cloud provider's guidance to determine if additional action is required. Patch status is vendor-dependent; check vendor advisories for specific remediation details.
Description
Two vulnerabilities have been identified in the TPM 2.0 reference implementation: an information leakage vulnerability (CVE-2026-6726) allowing privileged local attackers to obtain credentials for falsified TPM keys, and a timing side-channel vulnerability (CVE-2026-6727) in RSA OAEP decryption that could enable decryption of ciphertexts encrypted to TPM-managed RSA keys. Exploitation requires privileged local access to the TPM command interface. Successful attacks could lead to forged TPM attestations and decryption of sensitive data. Multiple vendors have released firmware and software updates incorporating fixes. Users should apply these updates as provided by their platform or TPM vendor. Cloud providers using software TPMs may have also deployed patches and customers should consult their providers. The overall impact depends on the TPM implementation and usage context.