CVE-2026-85525
HIGHDescription
Improper OCSP response validation in the Snowflake Python, Go, JDBC, and Node.js drivers allowed a revoked TLS certificate to be accepted as valid, because OCSP responses were not reliably bound to the certificate being validated and definitive verification failures were treated as transient. A man-in-the-middle attacker holding a revoked certificate and its private key for a Snowflake or stage hostname could cause the driver to establish a TLS session to the attacker-controlled endpoint anyway, allowing the attacker to read and modify data transmitted within that connection. Successful exploitation requires that on-path position and the corresponding private key, and impact is limited to data carried within the intercepted connection. The fix is available in Snowflake Connector for Python v4.7.3, Snowflake Go Driver v2.2.0, Snowflake JDBC Driver v4.3.4 (including the snowflake-jdbc-fips and snowflake-jdbc-thin), and Snowflake Node.js Driver v3.3.0. Users must manually upgrade.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 1% of all known CVEs.
References
Related Vulnerabilities
Other CWE-295 (Improper Certificate Validation) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2015-4000 | Low | 3.7 | 100% | - | Fix |
| CVE-2020-0601 | High | 8.1 | 89% | KEV | Fix |
| CVE-2009-3555 | Critical | 9.8 | 87% | - | Fix |
| CVE-2022-26923 | High | 8.8 | 84% | KEV | Fix |
| CVE-2023-27823 | Critical | 9.8 | 54% | - | - |
| CVE-2022-42979 | High | 8.8 | 24% | - | - |
Common questions
How do I fix CVE-2026-85525?
No published fix for CVE-2026-85525 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-85525 being actively exploited?
Not that we know of. CVE-2026-85525 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.10% is the estimated probability that it will be exploited in the next 30 days. That is higher than 1% of all scored CVEs.
How severe is CVE-2026-85525?
CVE-2026-85525 has a CVSS v3 base score of 7.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-85525
Markdown
[](https://tridentstack.com/cve/CVE-2026-85525)HTML
<a href="https://tridentstack.com/cve/CVE-2026-85525"><img src="https://tridentstack.com/cve/badge/CVE-2026-85525.svg" alt="CVE-2026-85525"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-10.