Credential forgery via stale object-slot reuse
Published Aug 11, 2026 · Updated Aug 11, 2026
Information leakage in Trusted Computing Group TPM 2.0 reference code through v184 allows local users to forge TPM key credentials. Stale key or data object state, including the object Name, remains after a slot is flushed and is reused as a hash context without a type check by TPM2_Certify. Elevated access to the local TPM command interface is required; successful abuse yields CA-issued credentials for falsified keys and fraudulent device attestations.
Summary
What happened
Information leakage in Trusted Computing Group TPM 2.0 reference code through v184 allows local users to forge TPM key credentials. Stale key or data object state, including the object Name, remains after a slot is flushed and is reused as a hash context without a type check by TPM2_Certify. Elevated access to the local TPM command interface is required; successful abuse yields CA-issued credentials for falsified keys and fraudulent device attestations.
The record
- CVE
- CVE-2026-6726
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Trusted Computing Group
- Product
- Trusted Platform Module 2.0 Library Specification
- Classifications
- CWE-226, CWE-704, T1649
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=v184
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo