Skip to content
Noroxi
NVD / CVE Program· CNA SNOWFLAKE

CVE-2026-86597: Sensitive information written to logs by Snowflake drivers

MediumCVSS 6.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.08% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Snowflake Snowflake Connector for Python 4.7.3; Snowflake Snowflake Go Driver 2.2.0; Snowflake Snowflake JDBC Driver 4.3.4.

Low priority for now. Upgrade to Snowflake Snowflake Connector for Python 4.7.3; Snowflake Snowflake Go Driver 2.2.0; Snowflake Snowflake JDBC Driver 4.3.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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
Sep 8, 2026
Updated
Sep 10, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · SNOWFLAKE
6.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-86597

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for snowflake records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (SNOWFLAKE). Independent of NVD's CPE analysis and usually ahead of it.

  • Snowflake Snowflake Connector for Python

    • before 4.7.3affected · python

  • Snowflake Snowflake Go Driver

    • up to and including 1.19.1affected · semver
    • 2.0.0 and later · before 2.2.0affected · semver

  • Snowflake Snowflake JDBC Driver

    • before 4.3.4affected · maven

  • Snowflake Snowflake JDBC Driver (FIPS)

    • before 4.3.4affected · maven

  • Snowflake Snowflake JDBC Driver (Thin)

    • before 4.3.4affected · maven

  • Snowflake Snowflake Node.js Driver

    • before 3.3.0affected · semver

  • Snowflake Snowflake ODBC Driver

    • 3.16.0 and later · before 3.20.0affected · semver

  • Snowflake Snowflake PHP PDO Driver

    • 3.4.0 and later · before 4.2.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/snowflakedb/gosnowflakefrom 0—
Gogithub.com/snowflakedb/gosnowflakeup to and including 1.19.1—
Gogithub.com/snowflakedb/gosnowflake/v2before 2.2.02.2.0
Mavennet.snowflake:snowflake-jdbcbefore 4.3.44.3.4
Mavennet.snowflake:snowflake-jdbc-fipsbefore 4.3.44.3.4
Mavennet.snowflake:snowflake-jdbc-thinbefore 4.3.44.3.4
npmsnowflake-sdkbefore 3.3.03.3.0
PyPIsnowflake-connector-pythonbefore 4.7.34.7.3

Same product

snowflake: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-15925Improper TLS Hostname Verification in Snowflake Connector for Python
    36Monitor
  • CVE-2026-123859SQL Injection via unescaped DataFrame column names in Snowflake Connector for Python and Snowflake Connector for Python (Universal Core)
    32Monitor
  • CVE-2026-86600Workload identity attestation generated before login host validation in Snowflake drivers
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-85525Sep 4, 2026 · Improper OCSP response validation in Snowflake drivers
    29Monitor
  • Later →CVE-2026-114456Nov 4, 2026 · Missing origin validation for the externalbrowser authenticator callback in multiple Snowflake client drivers
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Snowflake Snowflake Connector for Python4.7.3Vendor (CNA)
Snowflake Snowflake Go Driver2.2.0Vendor (CNA)
Snowflake Snowflake JDBC Driver4.3.4Vendor (CNA)
Snowflake Snowflake JDBC Driver (FIPS)4.3.4Vendor (CNA)
Snowflake Snowflake JDBC Driver (Thin)4.3.4Vendor (CNA)
Snowflake Snowflake Node.js Driver3.3.0Vendor (CNA)
Snowflake Snowflake ODBC Driver3.20.0Vendor (CNA)
Snowflake Snowflake PHP PDO Driver4.2.0Vendor (CNA)
Go:github.com/snowflakedb/gosnowflake/v22.2.0Package registry (OSV)
Maven:net.snowflake:snowflake-jdbc4.3.4Package registry (OSV)
Maven:net.snowflake:snowflake-jdbc-fips4.3.4Package registry (OSV)
Maven:net.snowflake:snowflake-jdbc-thin4.3.4Package registry (OSV)
npm:snowflake-sdk3.3.0Package registry (OSV)
PyPI:snowflake-connector-python4.7.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-532 · Insertion of Sensitive Information into Log File

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records