HighCVE-2026-86600

Workload identity attestation generated before login host validation in Snowflake drivers (CVE-2026-86600)

Published 08.09.2026Last modified 10.09.2026Sources: CVE.org

What is affected, what to do

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 3.14.1..4.7.3
Snowflake Go Driver lte 1.15.0..1.19.1
Snowflake Go Driver lt 2.0.0..2.2.0
Snowflake JDBC Driver lt 3.24.0..4.3.4
Snowflake JDBC Driver (FIPS) lt 3.24.0..4.3.4
Snowflake JDBC Driver (Thin) lt 3.24.0..4.3.4
Snowflake Node.js Driver lt 2.1.1..3.3.0
Snowflake Connector for .NET lt 4.7.0..6.1.0
Snowflake ODBC Driver lt 3.9.0..3.20.0
Snowflake PHP PDO Driver lt 3.6.0..4.2.0
Snowflake Libsnowflakeclient lt 2.2.0..2.10.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 Connector for .NET 6.1.0
Snowflake ODBC Driver 3.20.0
Snowflake PHP PDO Driver 4.2.0
Snowflake Libsnowflakeclient 2.10.0

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

Metrics

8.2

Priority

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

Source: Vendor (CNA), CVSS v3

8.2

CVSS v3

Severity High on the scale from 0 to 10.

Source: CVE.org

0.5 %

EPSS score

Low — model estimates < 1% exploitation likelihood.

Source: FIRST EPSS, percentile 43.4

Show all metrics

Severity: High
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: 82.40 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: 8.2 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: 8.2
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.5 %; 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: 43.4; High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
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: 08.09.2026
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-522, CWE-441

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: High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
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

In affected Snowflake drivers, WORKLOAD_IDENTITY authentication requests a cloud workload-identity token and attaches it to the login request without verifying that the configured host is a Snowflake endpoint. An attacker who can modify the connection configuration can cause the driver to mint a fresh attestation and send it to a host they control. The captured token can be replayed to Snowflake for its remaining lifetime in accounts where that workload identity is already registered. On Azure, the token audience is also taken from connection configuration. Combined with an attacker-controlled host, the driver can request a Managed Identity access token scoped to a non-Snowflake Azure resource and deliver it to the attacker. That path is the only case in which impact extends beyond Snowflake; it is bounded by the token lifetime and the managed identity’s permissions. Successful exploitation requires WORKLOAD_IDENTITY authentication on a workload that already has an ambient cloud identity. Patched driver versions restrict this authenticator to recognized Snowflake hosts. Users must manually upgrade.

Source: 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 versions	Fixed in
Snowflake	Snowflake Connector for .NET	`4.7.0 – < 6.1.0`	`6.1.0`
Snowflake	Snowflake Connector for Python	`3.14.1 – < 4.7.3`	`4.7.3`
Snowflake	Snowflake Go Driver	`1.15.0 – ≤ 1.19.1` `2.0.0 – < 2.2.0`	— `2.2.0`
Snowflake	Snowflake JDBC Driver	`3.24.0 – < 4.3.4`	`4.3.4`
Snowflake	Snowflake JDBC Driver (FIPS)	`3.24.0 – < 4.3.4`	`4.3.4`
Snowflake	Snowflake JDBC Driver (Thin)	`3.24.0 – < 4.3.4`	`4.3.4`
Snowflake	Snowflake Libsnowflakeclient	`2.2.0 – < 2.10.0`	`2.10.0`
Snowflake	Snowflake Node.js Driver	`2.1.1 – < 3.3.0`	`3.3.0`
Snowflake	Snowflake ODBC Driver	`3.9.0 – < 3.20.0`	`3.20.0`
Snowflake	Snowflake PHP PDO Driver	`3.6.0 – < 4.2.0`	`4.2.0`

Vendors and products

Weakness classes (CWE)

CWE-522Insufficiently Protected Credentials
Class
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Entry at MITRE CWE-522
CWE-441Unintended Proxy or Intermediary ('Confused Deputy')
Class
The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.
Entry at MITRE CWE-441

References & sources

github.comSnowflake Connector for Python Release Notes
docs.snowflake.comSnowflake Go Driver Release Notes
docs.snowflake.comSnowflake JDBC Driver Release Notes
docs.snowflake.comSnowflake Node.js Driver Release Notes
docs.snowflake.comSnowflake Connector for .NET Release Notes
docs.snowflake.comSnowflake ODBC Driver Release Notes
docs.snowflake.comSnowflake PHP PDO Driver Release Notes
github.comSnowflake Libsnowflakeclient Release Notes

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).

10.09.2026Record modified412d305a…

1 individual change: Affected versions (publisher)

Show the original change

Individual changes of this event as published by NVD
Type	Action	Before	After
Affected versions (publisher)	added	—	Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/86xxx/CVE-2026-86600.json">CVE-2026-86600</a>

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

08.09.2026Record modifiedCISA ADP

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

Show the original change

Individual changes of this event as published by NVD
Type	Action	Before	After
SSVC assessment	added	—	{"id":"CVE-2026-86600","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-08T18:03:59.388056Z"}

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

08.09.2026Received412d305a…

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

Weakness type: CWE-441, CWE-522

Description added or changed

New references:

and 4 more references

Show 13 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Description	added	—	In affected Snowflake drivers, WORKLOAD_IDENTITY authentication requests a cloud workload-identity token and attaches it to the login request without verifying that the configured host is a Snowflake endpoint. An attacker who can modify the connection configuration can cause the driver to mint a fresh attestation and send it to a host they control. The captured token can be replayed to Snowflake for its remaining lifetime in accounts where that workload identity is already registered. On Azure, the token audience is also taken from connection configuration. Combined with an attacker-controlled host, the driver can request a Managed Identity access token scoped to a non-Snowflake Azure resource and deliver it to the attacker. That path is the only case in which impact extends beyond Snowflake; it is bounded by the token lifetime and the managed identity’s permissions. Successful exploitation requires WORKLOAD_IDENTITY authentication on a workload that already has an ambient cloud identity. Patched driver versions restrict this authenticator to recognized Snowflake hosts. Users must manually upgrade.
CVSS	added	—	AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
Weakness type (CWE)	added	—	CWE-441
Weakness type (CWE)	added	—	CWE-522
Affected versions (publisher)	added	—	New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/86xxx/CVE-2026-86600.json">CVE-2026-86600</a>
Reference	added	—	https://docs.snowflake.com/en/release-notes/clients-drivers/dotnet-2026#version-610-september-3-2026
Reference	added	—	https://docs.snowflake.com/en/release-notes/clients-drivers/golang-2026#version-220-sep-03-2026
Reference	added	—	https://docs.snowflake.com/en/release-notes/clients-drivers/jdbc-2026#version-434-sep-03-2026
Reference	added	—	https://docs.snowflake.com/en/release-notes/clients-drivers/nodejs-2026#version-330-september-3-2026
Reference	added	—	https://docs.snowflake.com/en/release-notes/clients-drivers/odbc-2026#version-3200-sep-3-2026
Reference	added	—	https://docs.snowflake.com/en/release-notes/clients-drivers/php-pdo-2026#version-420-sep-3-2026
Reference	added	—	https://github.com/snowflakedb/libsnowflakeclient/releases/tag/v2.10.0
Reference	added	—	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.

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