Untrusted enclave acceptance via omitted PCR values
Published Nov 12, 2025 · Updated Nov 12, 2025
Improper enclave attestation verification in Evervault Go SDK before 1.3.2 allows attackers to make clients trust unapproved enclaves. The verifyPCRs path converted absent PCR map entries to empty strings, and Equal treated paired empty values as matches, allowing an omitted PCR8 to satisfy expectations. Applications checking only PCR8 are most exposed; in Evervault-hosted environments, exploitation also requires serving requests from specific Evervault domain names.
Summary
What happened
Improper enclave attestation verification in Evervault Go SDK before 1.3.2 allows attackers to make clients trust unapproved enclaves. The verifyPCRs path converted absent PCR map entries to empty strings, and Equal treated paired empty values as matches, allowing an omitted PCR8 to satisfy expectations. Applications checking only PCR8 are most exposed; in Evervault-hosted environments, exploitation also requires serving requests from specific Evervault domain names.
The record
- CVE
- CVE-2025-64186
- Published
- Nov 12, 2025
- Updated
- Nov 12, 2025
- Vendor
- Evervault
- Product
- Evervault Go SDK
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 12, 2025Record 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=< 1.3.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.
Weakness, pattern, technique
Public exploit references
- GHSA-88h9-77c7-p6w4 embedded proof of conceptproof of concept · unverified
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