CVE-2026-86597: Sensitive information written to logs by Snowflake drivers
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Operational
Manually upgrade to the patched versions listed above (for Snowflake Python, Go, JDBC, Node.js, PHP PDO, and ODBC drivers).
- Operational
Securely delete previously generated Snowflake driver diagnostic logs that may contain sensitive information (e.g., authentication tokens, query-result encryption keys, pre-signed cloud-storage URLs, and SAML assertions) when retention is not required, especially for log destinations the attacker could read.
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker needs read access to the diagnostic-log destination. This may include the local filesystem, a log aggregation service, or a CI/CD artifact store that contains the affected logs.
What information could be exposed through affected logs?
Affected log paths may contain authentication tokens, query-result encryption keys, pre-signed cloud-storage URLs, and SAML assertions. These materials could be used to authenticate to the relevant Snowflake account or access the associated cloud-storage object if they remain valid.
Are previously generated logs still a concern after upgrading?
Yes. Upgrading prevents the identified logging behavior in patched versions, but it does not remove sensitive data already written to existing diagnostic logs. Securely delete previously generated diagnostic logs where retention is not required.
What limits the impact of exposed log data?
The practical impact is limited by the lifetime of the exposed credential or assertion and by the scope of the associated cloud-storage object. An attacker must also be able to read the location where the logs were stored.