CVE-2025-64186: Evervault Go SDK Incomplete PCR Validation Vulnerability

HIGH
Advisory Identifier: GHSA-88h9-77c7-p6w4
CVSS 8.7
CWE-347
Published
Advisory Summary

CVE-2025-64186 is a HIGH (CVSS 8.7) incomplete pcr validation vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Evervault Go SDK libraries in the Go ecosystem. The issue involves incomplete pcr validation in enclave attestation for non-evervault hosted enclaves. Remediation is available by upgrading affected packages to version 1.3.2.

CVE-2025-64186 at a Glance

CVE Identifier CVE-2025-64186
GHSA Identifier GHSA-88h9-77c7-p6w4
Severity HIGH
CVSS v3.1 Base Score 8.7
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Evervault Go SDK
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-64186

To remediate this vulnerability, upgrade all affected Evervault Go SDK dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/evervault/evervault-go fixed: 1.3.2
Upgrade github.com/evervault/evervault-go to 1.3.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/evervault/evervault-go

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-64186, inspect your project dependencies for Evervault Go SDK:

inspect dependencies for github.com/evervault/evervault-go

Analyze the terminal output to locate any version of Evervault Go SDK in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Evervault Go SDK, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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) } ```

CVE-2025-64186 Affected Evervault Go SDK Versions

1 component(s)
Fixed Versions:
1.3.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/evervault/evervault-go
Go
< 1.3.2
1.3.2

References

Frequently Asked Questions

What is CVE-2025-64186?
CVE-2025-64186 is a security vulnerability in Evervault Go SDK involving Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves under CWE-347: Improper Verification of Cryptographic Signature.
Which Evervault Go SDK versions are affected?
Affected versions include releases prior to 1.3.2 across affected packages: github.com/evervault/evervault-go.
What version fixes CVE-2025-64186?
Upgrading to 1.3.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/evervault/evervault-go affected?
Yes, github.com/evervault/evervault-go is affected in releases prior to 1.3.2. Upgrade your dependency to 1.3.2 or later.
What is the CVSS score of CVE-2025-64186?
CVE-2025-64186 has a CVSS v3.1 base score of 8.7 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2025-64186?
CVE-2025-64186 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check Go dependencies for CVE-2025-64186?
Run the dependency tree command: 'inspect dependencies for github.com/evervault/evervault-go'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-88h9-77c7-p6w4",
  "modified" : "2025-11-18T17:00:18Z",
  "published" : "2025-11-12T21:45:06Z",
  "aliases" : [ "CVE-2025-64186" ],
  "summary" : "Evervault Go SDK: Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves",
  "details" : "### Summary\n\nA 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.\n\nThe 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. \n\nThe 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.\n \n\n### Patches\nThe 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.\n\n### Workarounds\nIf you are using evervault-go to attest Enclaves that are hosted outside of Evervault environments and cannot upgrade:\n\n1) Modify your application logic to fail verification if PCR8 is not explicitly present and non-empty\n2) Add custom pre-validation to reject documents that omit any required PCRs.\n\n### POC\n```\npackage evervault\nimport (\n        \"testing\"\n\n        \"github.com/evervault/evervault-go/attestation\"\n        \"github.com/stretchr/testify/assert\"\n        \"github.com/hf/nitrite\"\n)\n\n\nfunc TestVulnerableCompare(t *testing.T) {\n          assert := assert.New(t)\n          // arrange\n          expectedPCRs := []attestation.PCRs{\n                attestation.PCRs{\n                      PCR0:\n\"000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001\",\n                      PCR1:\n\"000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002\",\n                      PCR2:\n\"000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003\",\n                      PCR8:\n\"000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004\",\n                     },\n           }\n            actualDocument := nitrite.Document {}\n            actualDocument.PCRs = map[uint][]byte{\n                    10: make([]byte, 32),\n            }\n            // act\n            v := verifyPCRs(expectedPCRs, actualDocument)\n            \n            // assert\n            // Verify should not pass but it does\n            \n            assert.Equal(true, v)\n}\n```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/evervault/evervault-go"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.3.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/evervault/evervault-go/security/advisories/GHSA-88h9-77c7-p6w4"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-64186"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/evervault/evervault-go/pull/48"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/evervault/evervault-go/commit/7c824d289bba11ec0bea46a338023f5b128bbb28"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/evervault/evervault-go"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-12T21:45:06Z",
    "nvd_published_at" : "2025-11-12T21:15:53Z"
  }
}