Strix
73.2K

CVE-2026-86600

HIGHCVSS 8.2/10EPSS 0.31%

Last modified

CVE-2026-86600 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. 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. EPSS estimates a 0.31% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
8.2/10

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

EPSS Probability
0.31%

23.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
SnowflakeSnowflake Connector for Python>= 3.14.1, < 4.7.3
SnowflakeSnowflake Go Driver>= 1.15.0, <= 1.19.1
SnowflakeSnowflake Go Driver>= 2.0.0, < 2.2.0
SnowflakeSnowflake JDBC Driver>= 3.24.0, < 4.3.4
SnowflakeSnowflake JDBC Driver (FIPS)>= 3.24.0, < 4.3.4
SnowflakeSnowflake JDBC Driver (Thin)>= 3.24.0, < 4.3.4
SnowflakeSnowflake Node.js Driver>= 2.1.1, < 3.3.0
SnowflakeSnowflake Connector for .NET>= 4.7.0, < 6.1.0
SnowflakeSnowflake ODBC Driver>= 3.9.0, < 3.20.0
SnowflakeSnowflake PHP PDO Driver>= 3.6.0, < 4.2.0
SnowflakeSnowflake Libsnowflakeclient>= 2.2.0, < 2.10.0

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-86600?
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.
How severe is CVE-2026-86600?
CVE-2026-86600 has a CVSS score of 8.2/10 (HIGH severity). The EPSS model estimates a 0.31% probability of exploitation in the next 30 days.
How do I fix CVE-2026-86600?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-86600?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST