CVE-2026-86597

Sensitive information written to logs by Snowflake drivers

MEDIUM
6.5
CVSS Score
Published: September 8, 2026 at 08:24 AM UTC
Updated: September 10, 2026 at 04:18 PM UTC
10 products affected across 2 vendorsSnowflake JdbcGosnowflakePdo Snowflake

Using Snowflake Connector for Python by Snowflake?

Get instant alerts when new vulnerabilities affect Snowflake Connector for Python - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

Insertion of sensitive information into log files in the Snowflake Python, Go, JDBC, Node.js, PHP PDO, and ODBC drivers allowed authentication tokens, query-result encryption keys, pre-signed cloud-storage URLs, and SAML assertions to be written to diagnostic logs in circumstances where the available log redaction did not cover all affected log paths and data types. An attacker with read access to the log destination, whether the local filesystem, a log aggregation service, or a CI/CD artifact store, could obtain credentials and decryption keys that, if still valid at the time of access, could be used to authenticate to the corresponding Snowflake account or cloud-storage object. Successful exploitation requires read access to the log destination, and impact is bounded by credential lifetime and object scope. The fix is available in the patched versions listed above. Users must manually upgrade and should securely delete previously generated diagnostic logs containing sensitive information where retention is not required.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 1.19.12.0.0 ≤ v < 2.2.02.0.0
Affected range stops below 2.2.0, so it looks safe — our inference, not a vendor statement
v < 4.7.3
Affected range stops below 4.7.3, so it looks safe — our inference, not a vendor statement
v < 4.3.4
Affected range stops below 4.3.4, so it looks safe — our inference, not a vendor statement
v < 3.3.0
Affected range stops below 3.3.0, so it looks safe — our inference, not a vendor statement
3.16.0 ≤ v < 3.20.03.16.0
Affected range stops below 3.20.0, so it looks safe — our inference, not a vendor statement
3.4.0 ≤ v < 4.2.03.4.0
Affected range stops below 4.2.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMSNOWFLAKE
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card