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.
CVE-2026-86600
Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. a secondary CVSS source baseline 8.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(high)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
September 8, 2026
Last Modified
September 10, 2026
Advisory Details (8)
Auto-updated Sep 8, 2026Internal Release
Patch available: snowflakedb/libsnowflakeclient v2.10.0
https://github.com/snowflakedb/libsnowflakeclient/releases/tag/v2.10.0PHP PDO Driver for Snowflake release notes for 2026 | Snowflake Documentation
https://docs.snowflake.com/en/release-notes/clients-drivers/php-pdo-2026#version-420-sep-3-2026ODBC Driver release notes for 2026 | Snowflake Documentation
https://docs.snowflake.com/en/release-notes/clients-drivers/odbc-2026#version-3200-sep-3-2026.NET Driver release notes for 2026 | Snowflake Documentation
https://docs.snowflake.com/en/release-notes/clients-drivers/dotnet-2026#version-610-september-3-2026Node.js Driver release notes for 2026 | Snowflake Documentation
https://docs.snowflake.com/en/release-notes/clients-drivers/nodejs-2026#version-330-september-3-2026JDBC Driver release notes for 2026 | Snowflake Documentation
https://docs.snowflake.com/en/release-notes/clients-drivers/jdbc-2026#version-434-sep-03-2026Go Snowflake Driver release notes for 2026 | Snowflake Documentation
https://docs.snowflake.com/en/release-notes/clients-drivers/golang-2026#version-220-sep-03-20264.7.3
Patch available: snowflakedb/snowflake-connector-python v4.7.3
https://github.com/snowflakedb/snowflake-connector-python/releases/tag/v4.7.3Vendor Advisories for CVE-2026-86600(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 26× in last 7d / 45× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 23:23 UTCEG score recompute
- 2026-09-18 23:23 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 10:59 UTCGHSA enrichment
- 2026-09-17 22:35 UTCEG score recompute
- 2026-09-17 22:35 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 10:05 UTCGHSA enrichment
- 2026-09-16 21:41 UTCEG score recompute
- 2026-09-16 21:41 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 09:16 UTCEG score recompute
- 2026-09-16 09:16 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 20:51 UTCGHSA enrichment
- 2026-09-15 08:13 UTCEG score recompute
- 2026-09-15 08:13 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 19:48 UTCGHSA enrichment
- 2026-09-14 07:24 UTCGHSA enrichment
- 2026-09-13 19:00 UTCEG score recompute
- 2026-09-13 19:00 UTCGHSA enrichment
- 2026-09-13 06:36 UTCGHSA enrichment
- 2026-09-12 18:12 UTCEG score recompute
Show 20 moreShow fewer
- 2026-09-12 18:12 UTCGHSA enrichment
- 2026-09-12 05:48 UTCGHSA enrichment
- 2026-09-11 17:24 UTCEG score recompute
- 2026-09-11 17:24 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 04:48 UTCGHSA enrichment
- 2026-09-10 16:24 UTCEG score recompute
- 2026-09-10 16:24 UTCGHSA enrichment
- 2026-09-10 15:30 UTCEG score recompute
- 2026-09-10 15:30 UTCGHSA enrichment
- 2026-09-10 11:32 UTCEG score recompute
- 2026-09-10 11:32 UTCGHSA enrichment
- 2026-09-09 23:06 UTCGHSA enrichment
- 2026-09-09 08:13 UTCGHSA enrichment
- 2026-09-08 19:49 UTCEG score recompute
- 2026-09-08 19:49 UTCGHSA enrichment
- 2026-09-08 16:40 UTCEG score recompute
- 2026-09-08 15:51 UTCEG score recompute
- 2026-09-08 15:49 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-86600?
When was CVE-2026-86600 disclosed?
Is CVE-2026-86600 actively exploited?
What is the CVSS score of CVE-2026-86600?
How do I remediate CVE-2026-86600?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-86600
Is Your Infrastructure Affected by CVE-2026-86600?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.