CVE-2026-86597

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-08. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 10, 2026

Advisory Details (6)

Auto-updated Sep 8, 2026
Patch available. Sources: github_release.
generic

ODBC Driver release notes for 2026 | Snowflake Documentation

https://docs.snowflake.com/en/release-notes/clients-drivers/odbc-2026#version-3200-sep-3-2026
generic

PHP PDO Driver for Snowflake release notes for 2026 | Snowflake Documentation

https://docs.snowflake.com/en/release-notes/clients-drivers/php-pdo-2026#version-420-sep-3-2026
generic

Node.js Driver release notes for 2026 | Snowflake Documentation

https://docs.snowflake.com/en/release-notes/clients-drivers/nodejs-2026#version-330-september-3-2026
generic

JDBC Driver release notes for 2026 | Snowflake Documentation

https://docs.snowflake.com/en/release-notes/clients-drivers/jdbc-2026#version-434-sep-03-2026
generic

Go Snowflake Driver release notes for 2026 | Snowflake Documentation

https://docs.snowflake.com/en/release-notes/clients-drivers/golang-2026#version-220-sep-03-2026
github_release Patch Available

4.7.3

Patch available: snowflakedb/snowflake-connector-python v4.7.3

https://github.com/snowflakedb/snowflake-connector-python/releases/tag/v4.7.3

Vendor Advisories for CVE-2026-86597(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 11:22 UTCGHSA enrichment
  2. 2026-09-19 11:54 UTCEG score recompute
  3. 2026-09-19 11:54 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 12:27 UTCEG score recompute
  6. 2026-09-18 12:27 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 13:00 UTCEG score recompute
  9. 2026-09-17 13:00 UTCGHSA enrichment
  10. 2026-09-16 14:09 UTCEPSS rescore
  11. 2026-09-16 13:15 UTCGHSA enrichment
  12. 2026-09-15 13:44 UTCEG score recompute
  13. 2026-09-15 13:44 UTCGHSA enrichment
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-14 14:17 UTCEG score recompute
  17. 2026-09-14 14:17 UTCGHSA enrichment
  18. 2026-09-13 14:50 UTCGHSA enrichment
  19. 2026-09-12 15:19 UTCEG score recompute
  20. 2026-09-12 15:19 UTCGHSA enrichment
  21. 2026-09-11 15:52 UTCEG score recompute
  22. 2026-09-11 15:52 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-10 16:24 UTCEG score recompute
Show 15 more
  1. 2026-09-10 16:24 UTCGHSA enrichment
  2. 2026-09-10 15:40 UTCEG score recompute
  3. 2026-09-10 15:40 UTCGHSA enrichment
  4. 2026-09-09 19:17 UTCEG score recompute
  5. 2026-09-09 19:17 UTCGHSA enrichment
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-08 19:50 UTCGHSA enrichment
  8. 2026-09-08 13:38 UTCEG score recompute
  9. 2026-09-08 13:37 UTCGHSA enrichment
  10. 2026-09-08 12:35 UTCEG score recompute
  11. 2026-09-08 12:35 UTCGHSA enrichment
  12. 2026-09-08 09:39 UTCEG score recompute
  13. 2026-09-08 09:39 UTCGHSA enrichment
  14. 2026-09-08 08:36 UTCEG score recompute
  15. 2026-09-08 08:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-86597?
CVE-2026-86597 is a medium vulnerability published on September 8, 2026. 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…
When was CVE-2026-86597 disclosed?
CVE-2026-86597 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86597 actively exploited?
CVE-2026-86597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.6% of all scored CVEs.
What is the CVSS score of CVE-2026-86597?
CVE-2026-86597 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-86597?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86597, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86597

Explore →

Is Your Infrastructure Affected by CVE-2026-86597?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs