Attestation bypass via attacker-selected fallback verifier
Published Sep 16, 2026 · Updated Sep 19, 2026
Authentication bypass in OpenNHP 1.0.2 and earlier allows remote attackers to pass TEE attestation with crafted DHP evidence. The NewVerifier dispatcher treats an attacker-controlled test_purpose key as a request for FallbackVerifier, whose Verify method always returns success. Exploitation requires an enrolled measure and serial-number pair and yields successful attestation without proof of the corresponding hardware.
Summary
What happened
Authentication bypass in OpenNHP 1.0.2 and earlier allows remote attackers to pass TEE attestation with crafted DHP evidence. The NewVerifier dispatcher treats an attacker-controlled test_purpose key as a request for FallbackVerifier, whose Verify method always returns success. Exploitation requires an enrolled measure and serial-number pair and yields successful attestation without proof of the corresponding hardware.
The record
- CVE
- CVE-2026-92792
- Published
- Sep 16, 2026
- Updated
- Sep 19, 2026
- Vendor
- OpenNHP
- Product
- OpenNHP
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 19, 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 <=1.0.2
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started