CVE-2026-85525: Improper OCSP response validation in Snowflake drivers
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Snowflake Connector for Pythonto a version that resolves this vulnerability.Fixed in 4.7.3 - Upgrade
Upgrade
Snowflake Go Driverto a version that resolves this vulnerability.Fixed in 2.2.0 - Upgrade
Upgrade
Snowflake JDBC Driverto a version that resolves this vulnerability.Fixed in 4.3.4 - Upgrade
Upgrade
snowflake-jdbc-fipsto a version that resolves this vulnerability.Fixed in 4.3.4 - Upgrade
Upgrade
snowflake-jdbc-thinto a version that resolves this vulnerability.Fixed in 4.3.4 - Upgrade
Upgrade
Snowflake Node.js Driverto a version that resolves this vulnerability.Fixed in 3.3.0 - Operational
Manually upgrade the Snowflake drivers to the fixed versions: Python v4.7.3, Go v2.2.0, JDBC v4.3.4 (including snowflake-jdbc-fips and snowflake-jdbc-thin), and Node.js v3.3.0.
Event History
Frequently Asked Questions
What does an attacker need to exploit this issue?
The attacker must be in an on-path position between the driver and a Snowflake or stage hostname, and must possess a revoked certificate and its corresponding private key for that hostname. No authentication or user interaction is required, but the attack complexity is high because both conditions are necessary.
Which connections and data are at risk?
The issue affects TLS connections made through the Snowflake Python, Go, JDBC, and Node.js drivers. Exposure is limited to data transmitted within a connection that the attacker successfully intercepts; the attacker can read and modify that data.
Are users protected automatically by the available fix?
No. Users must manually upgrade to the patched driver versions listed in the relevant release information.