MediumCVE-2026-86597

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

    Published Last modified Sources: OSV, Hersteller, CVE.org

    What is affected, what to do

    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.

    Update Snowflake Connector for Python to version 4.7.3, Snowflake Go Driver to version 2.2.0, Snowflake JDBC Driver to version 4.3.4.

    Affected
    • Snowflake Connector for Python lt *..4.7.3
    • Snowflake Go Driver lte *..1.19.1
    • Snowflake Go Driver lt 2.0.0..2.2.0
    • Snowflake JDBC Driver lt *..4.3.4
    • Snowflake JDBC Driver (FIPS) lt *..4.3.4
    • Snowflake JDBC Driver (Thin) lt *..4.3.4
    • Snowflake Node.js Driver lt *..3.3.0
    • Snowflake PHP PDO Driver lt 3.4.0..4.2.0
    • Snowflake ODBC Driver lt 3.16.0..3.20.0
    Fixed in
    • Snowflake Connector for Python 4.7.3
    • Snowflake Go Driver 2.2.0
    • Snowflake JDBC Driver 4.3.4
    • Snowflake JDBC Driver (FIPS) 4.3.4
    • Snowflake JDBC Driver (Thin) 4.3.4
    • Snowflake Node.js Driver 3.3.0
    • Snowflake PHP PDO Driver 4.2.0
    • Snowflake ODBC Driver 3.20.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    6.5

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: OSV, Hersteller, CVE.org

    0.1 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 0.4

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    58.80 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.1 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    0.4
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-532

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    SnowflakeSnowflake Connector for Python
    • < 4.7.3
    • 4.7.3
    SnowflakeSnowflake Go Driver
    • 2.0.0 – < 2.2.0
    • ≤ 1.19.1
    • 2.2.0
    • —
    SnowflakeSnowflake JDBC Driver
    • < 4.3.4
    • 4.3.4
    SnowflakeSnowflake JDBC Driver (FIPS)
    • < 4.3.4
    • 4.3.4
    SnowflakeSnowflake JDBC Driver (Thin)
    • < 4.3.4
    • 4.3.4
    SnowflakeSnowflake Node.js Driver
    • < 3.3.0
    • 3.3.0
    SnowflakeSnowflake ODBC Driver
    • 3.16.0 – < 3.20.0
    • 3.20.0
    SnowflakeSnowflake PHP PDO Driver
    • 3.4.0 – < 4.2.0
    • 4.2.0
    gogithub.com/snowflakedb/gosnowflake
    • —
    • —
    gogithub.com/snowflakedb/gosnowflake/v2
    • —
    • —
    mavennet.snowflake:snowflake-jdbc
    • 3.6.10
    • 3.13.0
    • 3.10.2
    • 3.7.0
    • 3.13.33
    • 3.7.1
    • 3.24.0
    • 3.6.8
    • 3.6.16
    • 3.0.20
    • 3.21.0
    • 3.17.0
    • 3.6.4
    • 4.2.0
    • 3.12.15
    • 3.1.1
    • 3.16.1
    • 3.11.1
    • 3.14.1
    • 3.27.0
    • 3.3.1
    • 3.0.10
    • 3.0.6
    • 3.6.28
    • 3.13.7
    • 3.13.19
    • 3.8.8
    • 3.10.3
    • 3.8.5
    • 3.27.1
    • 3.2.1
    • 3.23.2
    • 3.12.12
    • 3.13.25
    • 3.0.0
    • 3.7.2
    • 3.5.5
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-532Insertion of Sensitive Information into Log File

      Base

      The product writes sensitive information to a log file.

      Entry at MITRE CWE-532

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modified412d305a…

      Description added or changed

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionchanged
      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 the patched versions listed above. Users must manually upgrade and should securely delete previously generated diagnostic logs containing sensitive information where retention is not required.
      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 versions (publisher)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/86xxx/CVE-2026-86597.json">CVE-2026-86597</a>

      Source identifier: 412d305a-227d-44f9-a262-a31ba44f2aea

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-86597","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-09-08T12:22:44.788390Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Received412d305a…

      CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

      Weakness type: CWE-532

      Description added or changed

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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 the patched versions listed above. Users must manually upgrade and should securely delete previously generated diagnostic logs containing sensitive information where retention is not required.
      CVSSadded
      —
      AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
      Weakness type (CWE)added
      —
      CWE-532
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/86xxx/CVE-2026-86597.json">CVE-2026-86597</a>
      Referenceadded
      —
      https://docs.snowflake.com/en/release-notes/clients-drivers/golang-2026#version-220-sep-03-2026
      Referenceadded
      —
      https://docs.snowflake.com/en/release-notes/clients-drivers/jdbc-2026#version-434-sep-03-2026
      Referenceadded
      —
      https://docs.snowflake.com/en/release-notes/clients-drivers/nodejs-2026#version-330-september-3-2026
      Referenceadded
      —
      https://docs.snowflake.com/en/release-notes/clients-drivers/odbc-2026#version-3200-sep-3-2026
      Referenceadded
      —
      https://docs.snowflake.com/en/release-notes/clients-drivers/php-pdo-2026#version-420-sep-3-2026
      Referenceadded
      —
      https://github.com/snowflakedb/snowflake-connector-python/releases/tag/v4.7.3

      Source identifier: 412d305a-227d-44f9-a262-a31ba44f2aea

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-86597
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-86597"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-86597.svg?lang=en" alt="CVE-2026-86597 – NEOSEC Intel" height="20"></a>