CVE-2026-85525
Last modified
CVE-2026-85525 is a high-severity vulnerability rated 7.4/10 on the CVSS scale. 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. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Snowflake | Snowflake Connector for Python | < 4.7.3 |
| Snowflake | Snowflake Go Driver | < 2.2.0 |
| Snowflake | Snowflake JDBC Driver | < 4.3.4 |
| Snowflake | Snowflake Node.js Driver | < 3.3.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-85525?
How severe is CVE-2026-85525?
How do I fix CVE-2026-85525?
How Strix Helps
- Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-85513A weakness has been identified in StackStorm st2 up to 3.9.0…6.3
- CVE-2026-85514A security vulnerability has been detected in StackStorm st2…6.3
- CVE-2026-85516A vulnerability was detected in code-projects Vehicle Manage…7.3
- CVE-2026-85517A flaw has been found in code-projects Vehicle Management Sy…5.3
- CVE-2026-8552Heap buffer overflow in GPU in Google Chrome on Android prio…4.3
- CVE-2026-85522A vulnerability was detected in valkey-io valkey up to 9.5.4…5.3
- CVE-2026-85528Improper input validation of the auto-configuration account …5.3
- CVE-2026-8553Use after free in GPU in Google Chrome prior to 148.0.7778.1…3.1
- CVE-2026-85533An authorization flaw in MISP allowed an authenticated user …7.6
- CVE-2026-85534A flaw was found in libsoup. When a client sends an HTTP/2 r…5.9
- CVE-2026-85538An incorrect authorization vulnerability in MISP allowed aut…8.3
- CVE-2026-8554Type Confusion in ANGLE in Google Chrome on Windows prior to…3.1
Are you affected by CVE-2026-85525?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
