CVE-2025-64186 Details
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.
A vulnerability exists in the Evervault Evervault-Go SDK's attestation verification process in versions prior to 1.3.2. This vulnerability may allow incomplete attestation documents to be accepted, potentially leading clients to trust an enclave operator that does not adhere to required integrity standards. The issue is less exploitable in Evervault-hosted environments, where an attacker would need to manipulate requests from specific Evervault domains. The vulnerability mainly impacts applications that rely solely on PCR8 for verification. While applications that check all PCR values are somewhat less affected, the issue can be mitigated by ensuring PCRs 0, 1, and 2 are properly validated.
Users can upgrade to Evervault-Go SDK version 1.3.2 or later, which addresses the vulnerability by improving the attestation document validation process. For those unable to upgrade, it is recommended to add custom pre-validation to reject documents missing required PCRs or to modify application logic to fail verification if PCR8 is not present and non-empty.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 14, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/evervault/evervault-go/security/advisories/GHSA-88h9-77c7-p6w4 | CISA-ADP | ExploitVendor Advisory |
| https://github.com/evervault/evervault-go/commit/7c824d289bba11ec0bea46a338023f5b128bbb28 | [email protected] | Patch |
| https://github.com/evervault/evervault-go/pull/48 | [email protected] | Issue TrackingPatch |
| https://github.com/evervault/evervault-go/security/advisories/GHSA-88h9-77c7-p6w4 | [email protected] | ExploitVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-347 | Improper Verification of Cryptographic Signature | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| evervault evervault | < 1.3.2 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 18, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 13, 2026 | Initial Analysis | [email protected] |
| Nov 14, 2025 | CVE Modified | CISA-ADP |
| Nov 12, 2025 | New CVE Received | [email protected] |