Skip to content
Fencer Intel
medium 6.5

CVE-2026-86597 json

Sensitive information written to logs by Snowflake drivers

published 2mo ago modified 27d ago also EUVD-2026-72672 , GHSA-qqj6-54q6-cxv6 , GO-2026-6665 , PYSEC-2026-4301

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits
0
none known

Summary

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 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), Snowflake Node.js Driver v3.3.0, Snowflake PHP PDO Driver v4.2.0, and Snowflake ODBC Driver v3.20.0. Users must manually upgrade and should securely delete previously generated diagnostic logs containing sensitive information where retention is not required.

Patch / fix

  • npm snowflake-sdk 3.3.0
  • pypi snowflake-connector-python 4.7.3
  • maven net.snowflake:snowflake-jdbc 4.3.4
  • maven net.snowflake:snowflake-jdbc-thin 4.3.4
  • maven net.snowflake:snowflake-jdbc-fips 4.3.4
  • go github.com/snowflakedb/gosnowflake/v2 2.2.0
  • Snowflake Snowflake Connector for Python 4.7.3
  • Snowflake Snowflake Go Driver 2.2.0
  • Snowflake Snowflake JDBC Driver 4.3.4
  • Snowflake Snowflake JDBC Driver (FIPS) 4.3.4
  • Snowflake Snowflake JDBC Driver (Thin) 4.3.4
  • Snowflake Snowflake Node.js Driver 3.3.0
  • Snowflake Snowflake PHP PDO Driver 4.2.0
  • Snowflake Snowflake ODBC Driver 3.20.0

Is CVE-2026-86597 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.09% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm snowflake-sdk
<3.3.0
3.3.0
pypi snowflake-connector-python
<4.7.3
4.7.3
go github.com/snowflakedb/gosnowflake
<=1.19.1
all versions
 no fix listed
maven net.snowflake:snowflake-jdbc
<4.3.4
4.3.4
maven net.snowflake:snowflake-jdbc-thin
<4.3.4
4.3.4
maven net.snowflake:snowflake-jdbc-fips
<4.3.4
4.3.4
go github.com/snowflakedb/gosnowflake/v2
<2.2.0
2.2.0

Affected products

  • Snowflake Snowflake Connector for Python
  • Snowflake Snowflake Go Driver
  • Snowflake Snowflake JDBC Driver
  • Snowflake Snowflake JDBC Driver (FIPS)
  • Snowflake Snowflake JDBC Driver (Thin)
  • Snowflake Snowflake Node.js Driver
  • Snowflake Snowflake PHP PDO Driver
  • Snowflake Snowflake ODBC Driver

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of snowflakedb/snowflake-connector-nodejs published their own advisory on GitHub. Reviewed sources take precedence over it.