Improper OCSP response validation in Snowflake drivers

Summary

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.

Timeline

1. Sep 4, 2026, 8:22 AM UTCCVE published
2. Sep 4, 2026, 7:40 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Sep 10, 2026, 3:44 PM UTCRecord last updated

Affected versions

• snowflake-connector-python

  fixed in 4.7.3

• github.com/snowflakedb/gosnowflake

  through 1.19.1

• github.com/snowflakedb/gosnowflake/v2

  From 2.0.0 · fixed in 2.2.0

• net.snowflake:snowflake-jdbc

  fixed in 4.3.4

• net.snowflake:snowflake-jdbc-fips

  fixed in 4.3.4

• net.snowflake:snowflake-jdbc-thin

  fixed in 4.3.4

• snowflake-sdk

  fixed in 3.3.0

References 4