ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-86597

Snowflake drivers writes sensitive information to logs

Published Oct 5, 2026 · catalog updated Oct 15, 2026 · Snowflake drivers writes sensitive

Check if you run it

No confirmed exploitation is on record for CVE-2026-86597. EPSS is 0.09%. Act only if a listed version of Snowflake drivers writes sensitive is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Snowflake drivers writes sensitive).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.09%
Remediation
Advisory link
Affected products
Go github.com/snowflakedb/gosnowflake · Go github.com/snowflakedb/gosnowflake/v2 · Maven net.snowflake:snowflake-jdbc · Maven net.snowflake:snowflake-jdbc-fips · Maven net.snowflake:snowflake-jdbc-thin · PyPI snowflake-connector-python

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/snowflakedb/gosnowflake0 → 1.19.1
  • Go github.com/snowflakedb/gosnowflake/v20 → 2.2.0
  • Maven net.snowflake:snowflake-jdbc0 → 4.3.4
  • Maven net.snowflake:snowflake-jdbc-fips0 → 4.3.4
  • Maven net.snowflake:snowflake-jdbc-thin0 → 4.3.4
  • PyPI snowflake-connector-python0 → 4.7.3
  • npm snowflake-sdk0 → 3.3.0

How to fix CVE-2026-86597

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-86597. EPSS is 0.09%. Act only if a listed version of Snowflake drivers writes sensitive is installed.

Which versions are affected?

Compare what you have installed with 0 → 1.19.1, 0 → 2.2.0, 0 → 4.3.4, 0 → 4.7.3, 0 → 3.3.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-532: Insertion of Sensitive Information into Log File. EPSS 0.09%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 5, 2026 · GitHub Advisory Database

    Detected

    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

  2. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    snowflake-sdk fixed in 3.3.0; snowflake-connector-python fixed in 4.7.3; net.snowflake:snowflake-jdbc fixed in 4.3.4; net.snowflake:snowflake-jdbc-thin fixed in 4.3.4

  3. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    snowflake-sdk fixed in 3.3.0

  4. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    snowflake-connector-python fixed in 4.7.3

  5. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    net.snowflake:snowflake-jdbc fixed in 4.3.4

  6. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    net.snowflake:snowflake-jdbc-thin fixed in 4.3.4

  7. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    net.snowflake:snowflake-jdbc-fips fixed in 4.3.4

  8. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    github.com/snowflakedb/gosnowflake/v2 fixed in 2.2.0

  9. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    github.com/snowflakedb/gosnowflake/v2 fixed in 2.2.0

  10. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    github.com/snowflakedb/gosnowflake fixed in 1.19.1

  11. Oct 15, 2026 · GitHub Advisory Database

    Updated

    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

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.