{"answers":{"affected":"3 open source packages ship an affected version, including github.com/evervault/evervault-go. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64186 exists.","fix":"Upgrade github.com/evervault/evervault-go to 1.3.2 or later.","what":"CVE-2025-64186 is a high-severity vulnerability in evervault-go, published on 12 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64186 and fix it if it is affected.\n\nWhat it is: CVE-2025-64186 is a high-severity vulnerability in evervault-go, published on 12 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64186 exists.\n\nAffected packages and fixed versions:\n- github.com/evervault/evervault-go (Go): affected all versions; fixed in 1.3.2\n- github.com/evervault/evervault-go (Go): affected all versions; fixed in 1.3.2\n- github.com/evervault/evervault-go (Go): affected all versions; fixed in 1.3.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-64186/ (Markdown: https://insights.sbomify.com/CVE-2025-64186/index.md)","id":"CVE-2025-64186","markdown":"https://insights.sbomify.com/CVE-2025-64186/index.md","name":"CVE-2025-64186","record":{"aliases":["GHSA-88h9-77c7-p6w4","GO-2025-4112"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Go SDK","requires_auth":"high_privilege","summary":"Incomplete PCR validation in the Evervault Go SDK allows attackers to bypass enclave attestation checks, potentially trusting malicious enclaves.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"evervault","vendor":"evervault"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Evervault Go SDK: Incomplete PCR Validation in Enclave Attestation for non-Evervault hosted Enclaves","id":"CVE-2025-64186","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"OctoPrint is vulnerable to XSS through Action Command Notifications and Prompts","id":"CVE-2025-64187"},"packages":[{"ecosystem":"Go","fixed":["1.3.2"],"introduced":["0"],"last_affected":[],"package":"github.com/evervault/evervault-go","purl":null,"source":"GHSA-88h9-77c7-p6w4"},{"ecosystem":"Go","fixed":["1.3.2"],"introduced":["0"],"last_affected":[],"package":"github.com/evervault/evervault-go","purl":"pkg:golang/github.com/evervault/evervault-go","source":"GHSA-88h9-77c7-p6w4"},{"ecosystem":"Go","fixed":["1.3.2"],"introduced":["0"],"last_affected":[],"package":"github.com/evervault/evervault-go","purl":"pkg:golang/github.com/evervault/evervault-go","source":"GO-2025-4112"}],"prev":{"headline":"Open OnDemand RPM packages create world writable locations","id":"CVE-2025-64185"},"products":["evervault-go"],"published":"2025-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-14","vendors":["evervault"]},"summary":"Incomplete PCR validation in the Evervault Go SDK allows attackers to bypass enclave attestation checks, potentially trusting malicious enclaves.","url":"https://insights.sbomify.com/CVE-2025-64186/"}