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.
CVE-2025-64186
“▲” beside the score: it is higher than NVD's CVSS score.
Score 8.7 from GitHub Security Advisory (severity: HIGH) published 2025-11-12. NVD baseline CVSS 6.5; sources differ by 2.2.
Also known asEUVD-2025-131929 (ENISA EUVD) · GHSA-88h9-77c7-p6w4 (GitHub Security Advisories) · GO-2025-4112 (OSV.dev)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 55EG Risk 55/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity87% × 45%Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.1%
- EPSS %ILE
- 3rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 12, 2025
Last Modified
October 18, 2026
Advisory Details (3)
Auto-updated Oct 18, 2026Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves · Advisory · evervault/evervault-go · GitHub
https://github.com/evervault/evervault-go/security/advisories/GHSA-88h9-77c7-p6w4Improve correctness of PCR check in enclaves Go SDK
Patch available: evervault/evervault-go v1.3.2 (PR #48 merged 2025-09-15)
https://github.com/evervault/evervault-go/pull/48commit 7c824d289bba (evervault/evervault-go)
Patch available: evervault/evervault-go v1.3.2 (contains commit 7c824d289bba)
https://github.com/evervault/evervault-go/commit/7c824d289bba11ec0bea46a338023f5b128bbb28Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/evervault/evervault-go @ 1.3.2 (fixes < 1.3.2) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/evervault/evervault-go | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 40× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 95 of 195 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-01 08:02 UTCGHSA enrichmentGHSA-88h9-77c7-p6w4 · GitHub severity HIGH · GitHub CVSS 8.7
- 2026-11-01 08:02 UTCEG score recompute▲ 2.20
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-28 04:55 UTCOSV refresh
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-25 16:11 UTCEG score recompute
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-18 20:39 UTCEG score recompute
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-18 05:20 UTCEG score recompute
- 2026-10-17 23:55 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 70 moreShow fewer
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-12 16:50 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-11 20:24 UTCEG score recompute
- 2026-10-11 18:36 UTCEG score recompute
- 2026-10-11 15:11 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-02 01:11 UTCOSV refresh
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-12 18:36 UTCOSV refresh
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-24 23:44 UTCOSV refresh
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-08 16:55 UTCOSV refresh
- 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2025-64186?
When was the CVE record for CVE-2025-64186 published?
Is CVE-2025-64186 actively exploited?
What is the CVSS score of CVE-2025-64186?
How do I remediate CVE-2025-64186?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-64186
Is Your Infrastructure Affected by CVE-2025-64186?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.