# CVE-2026-85525: Improper OCSP response validation in Snowflake drivers

> Man-in-the-middle attackers can bypass OCSP validation to intercept and modify data in Snowflake driver connections using revoked certificates.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** CLEANSTART-2026-LK90655, CLEANSTART-2026-QV01130, CLEANSTART-2026-UC39319, CLEANSTART-2026-XJ29486, CLEANSTART-2026-YH75013, GHSA-h6vc-8q8q-7wvw

## What is CVE-2026-85525?

CVE-2026-85525 is a high-severity vulnerability in Snowflake Connector for Python, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-85525?


## How do I fix CVE-2026-85525?

Upgrade to a fixed version.

## Is CVE-2026-85525 being exploited?

There is no known exploitation of CVE-2026-85525 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85525 and fix it if it is affected.

What it is: CVE-2026-85525 is a high-severity vulnerability in Snowflake Connector for Python, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85525 in the wild and no public exploit code.

Affected product: Snowflake Connector for Python. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85525/ (Markdown: https://insights.sbomify.com/CVE-2026-85525/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85525
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85525
- OSV: https://osv.dev/vulnerability/CVE-2026-85525

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85525/
Summaries are generated and may contain mistakes; the official description above is the record.