cve.bz

CVE-2026-86597 snowflake

6.5 mediumEPSS 0.09%Fix available

Medium (6.5) in snowflake. EPSS 0.09% estimated probability of exploitation activity in the next 30 days. Fixed in snowflake-sdk 3.3.0.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.09% (unchanged from 0.09% a week ago; 0.09% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • snowflake-sdk (npm): fixed in 3.3.0
  • snowflake-connector-python (PyPI): fixed in 4.7.3
  • net.snowflake:snowflake-jdbc (Maven): fixed in 4.3.4
  • net.snowflake:snowflake-jdbc-thin (Maven): fixed in 4.3.4
  • net.snowflake:snowflake-jdbc-fips (Maven): fixed in 4.3.4
  • github.com/snowflakedb/gosnowflake/v2 (Go): fixed in 2.2.0
  • SUSE, openSUSE: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-86597 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-86597?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-86597?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-86597 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Snowflake Connector for Pythonbefore 4.7.3
Snowflake Go Driverthrough 1.19.1
Snowflake Go Driverfrom 2.0.0 before 2.2.0
Snowflake JDBC Driverbefore 4.3.4
Snowflake JDBC Driver (FIPS)before 4.3.4
Snowflake JDBC Driver (Thin)before 4.3.4
Snowflake Node.js Driverbefore 3.3.0
Snowflake PHP PDO Driverfrom 3.4.0 before 4.2.0
Snowflake ODBC Driverfrom 3.16.0 before 3.20.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qqj6-54q6-cxv6npmsnowflake-sdk<3.3.03.3.0
GHSA-qqj6-54q6-cxv6PyPIsnowflake-connector-python<4.7.34.7.3
GHSA-qqj6-54q6-cxv6Gogithub.com/snowflakedb/gosnowflake<=1.19.1no fix published
GHSA-qqj6-54q6-cxv6Mavennet.snowflake:snowflake-jdbc<4.3.44.3.4
GHSA-qqj6-54q6-cxv6Mavennet.snowflake:snowflake-jdbc-thin<4.3.44.3.4
GHSA-qqj6-54q6-cxv6Mavennet.snowflake:snowflake-jdbc-fips<4.3.44.3.4
GHSA-qqj6-54q6-cxv6Gogithub.com/snowflakedb/gosnowflake/v2<2.2.02.2.0
GO-2026-6665Gogithub.com/snowflakedb/gosnowflakeall versionsno fix published
GO-2026-6665Gogithub.com/snowflakedb/gosnowflake/v2<2.2.02.2.0
PYSEC-2026-4301PyPIsnowflake-connector-python<4.7.34.7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1
openSUSELeap 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1openSUSE-SU-2026:22336-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON