Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go☕ Maven📦 npm🐍 PyPI
Not in CISA KEV
MEDIUM severity

Snowflake drivers writes sensitive information to logsGHSA-qqj6-54q6-cxv6

MEDIUM

GHSA-qqj6-54q6-cxv6 is a medium-severity (CVSS 6.5) CWE-532 vulnerability in github.com/snowflakedb/gosnowflake. A fix is available for github.com/snowflakedb/gosnowflake — see the affected versions and patch details below.

Also known asCVE-2026-86597GO-2026-6665PYSEC-2026-4301
Published
Updated
Affected
7 pkgs
Patched
6 / 7
Exploits
None indexed
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-qqj6-54q6-cxv6.

EPSS Exploitation Probability

via FIRST.org ↗
0.1%probability of exploitation in next 30 days
Lower Risk-0.03%
Lower risk than most CVEs0th percentile — riskier than 0% of all scored CVEsHighest risk
0.00%0.21%0.41%0.62%0.1%0.1%Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-qqj6-54q6-cxv6 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

7 pkgs affected
🐹github.com/snowflakedb/gosnowflake🐹github.com/snowflakedb/gosnowflake/v2☕net.snowflake:snowflake-jdbc☕net.snowflake:snowflake-jdbc-thin☕net.snowflake:snowflake-jdbc-fips📦snowflake-sdk🐍snowflake-connector-python

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go, Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

7 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/snowflakedb/gosnowflakeall versionsNo fix
🐹Gogithub.com/snowflakedb/gosnowflake/v2all versions2.2.0go get github.com/snowflakedb/gosnowflake/v2@v2.2.0
☕Mavennet.snowflake:snowflake-jdbcall versions4.3.4net.snowflake:snowflake-jdbc:4.3.4
☕Mavennet.snowflake:snowflake-jdbc-thinall versions4.3.4net.snowflake:snowflake-jdbc-thin:4.3.4
☕Mavennet.snowflake:snowflake-jdbc-fipsall versions4.3.4net.snowflake:snowflake-jdbc-fips:4.3.4
📦npmsnowflake-sdkall versions3.3.0npm install snowflake-sdk@3.3.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/snowflakedb/gosnowflake, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    No patched version of github.com/snowflakedb/gosnowflake has shipped for GHSA-qqj6-54q6-cxv6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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
O3 Security · Impact-Aware SCA

Is GHSA-qqj6-54q6-cxv6 in your dependencies?

Find it across Go, Maven, npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Snowflake drivers writes sensitive information to logs