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.
Published: 2026-09-04
Score: 7.4 High
EPSS: < 1% Very Low
KEV: No
Impact: Confidentiality and integrity of data transmitted over TLS may be compromised
Action: Immediate Patch
AI Analysis

Impact

The Snowflake Python, Go, JDBC, and Node.js drivers do not properly validate OCSP responses. A revoked TLS certificate can be accepted as valid because the OCSP response is not bound to the certificate and definitive validation failures are considered transient. A man‑in‑the‑middle attacker possessing a revoked certificate and its private key for a Snowflake or stage hostname could trick the driver into opening a TLS session to read and alter the data transmitted in that connection. The vulnerability is an OCSP validation weakness that permits data exfiltration or tampering.

Affected Systems

Snowflake Connector for Python, Snowflake Go Driver, Snowflake JDBC Driver, and Snowflake Node.js Driver. All releases prior to the patched versions announced in the Snowflake documentation (e.g., the Python driver v4.7.3 and the corresponding releases for Go, JDBC, and Node.js).

Risk and Exploitability

The CVSS score is 7.4, indicating a high severity. The EPSS score of 0.00105 indicates a very low probability of exploitation, though the vulnerability is still active and not listed in the CISA KEV catalog. Exploitation requires that the attacker be on the network path and possess a revoked certificate and its private key for the Snowflake or stage hostname data carried within the intercepted connection, but it enables data exfiltration and tampering. The attacker can therefore read and alter traffic, potentially compromising confidential information, without executing arbitrary code on the client or Snowflake servers.

Generated by OpenCVE AI on September 10, 2026 at 20:59 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade all Snowflake drivers to4.7.3, and the corresponding Go, JDBC, and Node.js driver versions identified in the release notes in the application, enforce proper OCSP response binding to the presented certificate and reject definitive failures instead of treating them as transient.
  • Apply network segmentation and enforce strict endpoint security to minimize the risk of on-path attackers intercepting TLS traffic.
  • Review and update any internal automation or CI pipelines that consume Snowflake drivers to ensure the new, secure versions are deployed and that no legacy driver binaries remain in use.

Generated by OpenCVE AI on September 10, 2026 at 20:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 10 Sep 2026 15:45:00 +0000

Type Values Removed Values Added
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 the patched versions listed above. Users must manually upgrade. 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.

Sat, 05 Sep 2026 22:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 04 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Important


Fri, 04 Sep 2026 08:30:00 +0000

Type Values Removed Values Added
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 the patched versions listed above. Users must manually upgrade.
Title Improper OCSP response validation in Snowflake drivers
Weaknesses CWE-295
CWE-347
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: SNOWFLAKE

Published:

Updated: 2026-09-10T15:44:00.239Z

Reserved: 2026-09-04T08:19:50.886Z

Link: CVE-2026-85525

cve-icon Vulnrichment

Updated: 2026-09-04T19:40:16.596Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-04T09:17:11.610

Modified: 2026-09-10T16:17:58.847

Link: CVE-2026-85525

cve-icon Redhat

Severity : Important

Publid Date: 2026-09-04T08:22:43Z

Links: CVE-2026-85525 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-10T21:15:14Z

Weaknesses
  • CWE-295

    Improper Certificate Validation

  • CWE-347

    Improper Verification of Cryptographic Signature