ZeroDay Findings
Sign inSign up

Findings

CVE-2026-86597

Snowflake drivers writes sensitive information to logs

Published Oct 5, 2026 · corrected/updated Oct 15, 2026 · evidence confidence high

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.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2026-86597 is a medium public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: github.com/snowflakedb/gosnowflake; github.com/snowflakedb/gosnowflake/v2 (0 → 2.2.0); net.snowflake:snowflake-jdbc (0 → 4.3.4); net.snowflake:snowflake-jdbc-fips (0 → 4.3.4). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 6.5. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-532. Sources contributing to this record: cve_org, github, osv, osv. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

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

    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

Affected

  • Go github.com/snowflakedb/gosnowflakeversion unspecified
  • 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

Sources

References