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 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.
Published: 2026-09-08
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Data Exposure
Action: Apply Patch
AI Analysis

Impact

Insertion of sensitive information into, JDBC, Node.js, PHP been identified. Authentication tokens, query‑result encryption keys, pre‑signed cloud‑storage URLs, and SAML assertions could be written to diagnostic logs when the available log redaction does not cover all affected log paths and data types. An attacker who can read the log destination—whether the local filesystem, a log aggregation service, or a CI/CD artifact store—could capture these credentials and decryption keys, and if still valid at the time of access could use them to authenticate to the corresponding Snowflake account or access cloud‑storage objects. Successful exploitation therefore requires only read access to the logs and is bounded by the lifetime of the credentials and the scope of the accessed objects. The issue is fixed 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 upgrade and securely delete previously generated diagnostic logs containing sensitive information where retention is not required.

Affected Systems

Snowflake Connector for Python (v4.7.3), Snowflake Go Driver (v2.2.0), Snowflake JDBC Driver (v4.3.4, includes FIPS and Thin variants), Snowflake Node.js Driver (v3.3.0), Snowflake ODBC Driver (v3.20.0), and Snowflake PHP PDO Driver (v4.2.0).

Risk and Exploitability

The vulnerability has a CVSS score of 6.5 <1%, suggesting a low predicted exploitation probability. It is not listed in the CISA KEV catalog. Attackers must have only read access to the logs and no special privileges beyond that. When logs are left unprotected, captured authentication tokens, encryption keys or pre‑signed URLs can be used to access Snowflake accounts or cloud‑storage while they remain valid.

Generated by OpenCVE AI on September 10, 2026 at 19:19 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Snowflake Connector for Python v4.7.3.
  • Upgrade to Snowflake Go Driver v2.2.0.
  • Upgrade to Snowflake JDBC Driver v4.3.4 (including fips and thin).
  • Upgrade to Snowflake Node.js Driver v3.3.0.
  • Upgrade to Snowflake ODBC Driver v3.20.0.
  • Upgrade to Snowflake PHP PDO Driver v4.2.0.
  • Delete diagnostic logs produced before the patches to remove any captured credentials.
  • Configure log redaction to cover all paths and data types, and/or store logs in a protected location accessible only by authorized personnel.

Generated by OpenCVE AI on September 10, 2026 at 19:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 10 Sep 2026 15:45:00 +0000

Type Values Removed Values Added
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. 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.

Tue, 08 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Snowflake
Snowflake snowflake-connector-python
Snowflake snowflake Go Driver
Snowflake snowflake Jdbc Driver
Snowflake snowflake Node.js Driver
Snowflake snowflake Odbc Driver
Snowflake snowflake Php Pdo Driver
Vendors & Products Snowflake
Snowflake snowflake-connector-python
Snowflake snowflake Go Driver
Snowflake snowflake Jdbc Driver
Snowflake snowflake Node.js Driver
Snowflake snowflake Odbc Driver
Snowflake snowflake Php Pdo Driver

Tue, 08 Sep 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Tue, 08 Sep 2026 08:30:00 +0000

Type Values Removed Values Added
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.
Title Sensitive information written to logs by Snowflake drivers
Weaknesses CWE-532
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N'}

Subscriptions

Snowflake Snowflake-connector-python Snowflake Go Driver Snowflake Jdbc Driver Snowflake Node.js Driver Snowflake Odbc Driver Snowflake Php Pdo Driver
cve-icon MITRE

Status: PUBLISHED

Assigner: SNOWFLAKE

Published:

Updated: 2026-09-10T15:37:52.230Z

Reserved: 2026-09-08T08:21:54.812Z

Link: CVE-2026-86597

cve-icon Vulnrichment

Updated: 2026-09-08T12:22:51.257Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-08T09:18:21.877

Modified: 2026-09-10T16:18:03.167

Link: CVE-2026-86597

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-10T19:30:06Z

Weaknesses
  • CWE-532

    Insertion of Sensitive Information into Log File