Categories
CVE-2026-86597 medium CVSS 6.5

Vulnerability in snowflake-sdk (CVE-2026-86597)

Summary

Vulnerability in snowflake-sdk (CVE-2026-86597). Confidential information can be exposed externally. Mitigation: upgrade to 3.3.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-86597 has been found in snowflake-sdk.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade snowflake-sdk to 3.3.0 or later.
If unsure, ask your IT team or search "snowflake-sdk CVE-2026-86597" on the vendor's site.

CVE-2026-86597 (snowflake-sdk) — CWE-532 / CVSS v3 6.5
Attack vector: local / no user interaction
Patched: 3.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-532) exists in snowflake-sdk.

📍 Affected scope

Check the vendor advisory for the affected versions of snowflake-sdk.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.3.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'snowflake-sdk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'snowflake-sdk' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で snowflake-sdk を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade snowflake-sdk to 3.3.0

    ステージング環境で 3.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm snowflake-sdk
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.0"}]}]
pip snowflake-connector-python
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.7.3"}]}]
go github.com/snowflakedb/gosnowflake
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
maven net.snowflake:snowflake-jdbc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.4"}]}]
maven net.snowflake:snowflake-jdbc-thin
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.4"}]}]
maven net.snowflake:snowflake-jdbc-fips
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.4"}]}]
go github.com/snowflakedb/gosnowflake/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details