Evervault Go SDK: Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves
Date: 2025-11
Affected: go/github.com/evervault/evervault-go
Attack vector: other
Category: vulnerability-disclosure
Severity: High
CVE: CVE-2025-64186
CWE: CWE-347
CVSS: 8.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N)

### Summary A vulnerability was identified in the `evervault-go` SDK’s attestation verification logic 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. ### Patches The identified issue has been addressed in version [1.3.2](https://github.com/evervault/evervault-go/pull/48) by validating attestation documents before storing in the cache, and replacing the naive equality checks with a new SatisfiedBy check. ### Workarounds If you are using evervault-go to attest Enclaves that are hosted outside of Evervault environments and cannot upgrade: 1) Modify your application logic to fail verification if PCR8 is not explicitly present and non-empty 2) Add custom pre-validation to reject documents that omit any required PCRs. ### POC ``` package evervault import ( "testing" "github.com/evervault/evervault-go/attestation" "github.com/stretchr/testify/assert" "github.c


Mitigations:

Architectural layers (MAESTRO):