Loading...
Skip to main content

CVE-2025-64186 — Vulnerability in...

HIGH

Evervault Go SDK: Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves

Published November 12, 2025Updated November 18, 2025Source: osv

Summary

### 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.com/hf/nitrite" ) func TestVulnerableCompare(t *testing.T) { assert := assert.New(t) // arrange expectedPCRs := []attestation.PCRs{ attestation.PCRs{ PCR0: "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001", PCR1: "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002", PCR2: "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003", PCR8: "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004", }, } actualDocument := nitrite.Document {} actualDocument.PCRs = map[uint][]byte{ 10: make([]byte, 32), } // act v := verifyPCRs(expectedPCRs, actualDocument) // assert // Verify should not pass but it does assert.Equal(true, v) } ```

Advisory Timeline

  • First published November 12, 2025 (334 days ago).
  • Last revised November 18, 2025 — 6 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Go
Update github.com/evervault/evervault-go to 1.3.2 or later
go get github.com/evervault/evervault-go@v1.3.2

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: go (1).

PackageEcosystemAffectedFixed In
github.com/evervault/evervault-go
go
All versions1.3.2

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-347
    Improper Verification of Cryptographic SignatureMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.7 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

Frequently Asked Questions

What is CVE-2025-64186?
Evervault Go SDK: Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.7/10).
How do I check if my project is affected by CVE-2025-64186?
CVE-2025-64186 affects github.com/evervault/evervault-go. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-64186 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.7

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-88h9-77c7-p6w4
GO-2025-4112

Related CVEs

  • CVE-2026-107809
    HIGH

    Nginx-UI AuthRequired token cookie fallback enables CSRF against management APIs

  • CVE-2026-107813
    HIGH

    Nginx UI: Incomplete fix of CVE-2026-84315 - the api/cluster router was not - wrapped in RequireSecureSession, so those sensitive mutations run without OTP step-up

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies