Back

HIGH

Improper OCSP response validation in Snowflake drivers

Published Sep 4, 2026

Description

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 products

Remediation

Red Hat statement

This vulnerability is rated as Important because improper OCSP response validation in Snowflake drivers, utilized by Red Hat OpenShift AI, could enable a man-in-the-middle attacker to intercept and modify data. Successful exploitation requires the attacker to possess a revoked TLS certificate and its corresponding private key for a Snowflake or stage hostname, along with a network position to intercept traffic, thereby limiting the attack surface.

Red Hat mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

References (8)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner SNOWFLAKE
Published Sep 4, 2026
Updated Sep 10, 2026
Reserved Sep 4, 2026
CISA Vulnrichment
Updated Sep 4, 2026
NVD
Status Awaiting Analysis
Modified Sep 10, 2026
Red Hat
Severity Important
Public date Sep 4, 2026