CVE-2025-64186 Evervault Go SDK: Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves
Incomplete PCR validation in the Evervault Go SDK allows attackers to bypass enclave attestation checks, potentially trusting malicious enclaves.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-64186?
CVE-2025-64186 is a high-severity vulnerability in evervault-go, published on 12 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Evervault is a payment security solution. A vulnerability was identified in the `evervault-go` SDK’s attestation verification logic in versions of `evervault-go` prior to 1.3.2 that may allow incomplete documents to pass validation. This may cause the client to trust an enclave operator that does not meet expected integrity guarantees. The exploitability of this issue is limited in Evervault-hosted environments as an attacker would require the pre-requisite ability to serve requests from specific evervault domain names, following from our ACME challenge based TLS certificate acquisition pipeline. The vulnerability primarily affects applications which only check PCR8. Though the efficacy is also reduced for applications that check all PCR values, the impact is largely remediated by checking PCR 0, 1 and 2. The identified issue has been addressed in version 1.3.2 by validating attestation documents before storing in the cache, and replacing the naive equality checks with a new SatisfiedBy check. Those who useevervault-go to attest Enclaves that are hosted outside of Evervault environments and cannot upgrade have two possible workarounds available. Modify the application logic to fail verification if PCR8 is not explicitly present and non-empty and/or add custom pre-validation to reject documents that omit any required PCRs.
Weakness: CWE-347
Which versions are affected by CVE-2025-64186?
3 open source packages ship an affected version, including github.com/evervault/evervault-go. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/evervault/evervault-go Go | All versions | 1.3.2 |
github.com/evervault/evervault-go Go | All versions | 1.3.2 |
github.com/evervault/evervault-go Go | All versions | 1.3.2 |
Products include Evervault Evervault.
How do I fix CVE-2025-64186?
Upgrade github.com/evervault/evervault-go to 1.3.2 or later.
Is CVE-2025-64186 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64186 exists.
Sources
Also known as GHSA-88h9-77c7-p6w4, GO-2025-4112.