Sensitive information written to logs by Snowflake drivers
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.7.3, 2.2.0, 4.3.4, 3.3.0, 4.2.0, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- snowflake-connector-python
fixed in 4.7.3
- github.com/snowflakedb/gosnowflake
through 1.19.1
- github.com/snowflakedb/gosnowflake/v2
From 2.0.0 · fixed in 2.2.0
- net.snowflake:snowflake-jdbc
fixed in 4.3.4
- net.snowflake:snowflake-jdbc-fips
fixed in 4.3.4
- net.snowflake:snowflake-jdbc-thin
fixed in 4.3.4
- snowflake-sdk
fixed in 3.3.0
- Snowflake Snowflake PHP PDO Driver
From 3.4.0 · fixed in 4.2.0
- Snowflake Snowflake ODBC Driver
From 3.16.0 · fixed in 3.20.0
- snowflake-sdknpm
fixed in 3.3.0
- snowflake-connector-pythonPyPI
fixed in 4.7.3
- github.com/snowflakedb/gosnowflakeGo
through 1.19.1
- net.snowflake:snowflake-jdbcMaven
fixed in 4.3.4
- net.snowflake:snowflake-jdbc-thinMaven
fixed in 4.3.4
- net.snowflake:snowflake-jdbc-fipsMaven
fixed in 4.3.4
- github.com/snowflakedb/gosnowflake/v2Go
fixed in 2.2.0
- github.com/snowflakedb/gosnowflakeGo
All versions
References 6
GitHub · snowflakedb/snowflake-connector-python
docs.snowflake.com
- en/release-notes/clients-drivers/golang-2026#version-220-sep-03-2026
- en/release-notes/clients-drivers/jdbc-2026#version-434-sep-03-2026
- en/release-notes/clients-drivers/nodejs-2026#version-330-september-3-2026
- en/release-notes/clients-drivers/php-pdo-2026#version-420-sep-3-2026
- en/release-notes/clients-drivers/odbc-2026#version-3200-sep-3-2026