CVE-2026-86597
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 0% of all known CVEs.
References
Related Vulnerabilities
Other CWE-532 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-1622 | Medium | 5.3 | 79% | - | - |
| CVE-2020-35234 | High | 7.5 | 65% | - | Fix |
| CVE-2023-43261 | High | 7.5 | 60% | - | Fix |
| CVE-2024-20440 | High | 7.5 | 52% | - | - |
| CVE-2018-3609 | High | 8.1 | 21% | - | - |
| CVE-2018-8719 | Medium | 5.3 | 16% | - | - |
Common questions
How do I fix CVE-2026-86597?
No published fix for CVE-2026-86597 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-86597 being actively exploited?
Not that we know of. CVE-2026-86597 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.09% is the estimated probability that it will be exploited in the next 30 days. That is higher than 0% of all scored CVEs.
How severe is CVE-2026-86597?
CVE-2026-86597 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-86597
Markdown
[](https://tridentstack.com/cve/CVE-2026-86597)HTML
<a href="https://tridentstack.com/cve/CVE-2026-86597"><img src="https://tridentstack.com/cve/badge/CVE-2026-86597.svg" alt="CVE-2026-86597"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-10.