CVE-2025-64186 is a high-severity (CVSS 8.7) CWE-347 vulnerability in github.com/evervault/evervault-go. A fix is available for github.com/evervault/evervault-go — see the affected versions and patch details below.
Evervault Go SDK: Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64186.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-64186 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/evervault/evervault-goReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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 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:
- Modify your application logic to fail verification if PCR8 is not explicitly present and non-empty
- 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)
}
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/evervault/evervault-go | all versions | 1.3.2go get github.com/evervault/evervault-go@v1.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/evervault/evervault-go, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/evervault/evervault-go to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64186 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-64186 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-64186. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-64186 in your dependencies?
O3 Security finds CVE-2025-64186 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.