The Snowflake client drivers obtain a cloud workload‑identity token and attach it to a login request without confirming that the configured host is a legitimate Snowflake endpoint. An attacker who can change the connection configuration can force the driver to mint this attestation and deliver it to a host they control. Because the token can later be replayed to Snowflake while it remains valid in accounts where the workload identity is already registered, the attacker may gain unauthorized access to Snowflake. On Azure, the driver also accepts a custom audience from the configuration, enabling the acquisition of a Managed Identity token scoped to a non‑Snowflake Azure resource and its delivery to an attacker. This path is the only one that extends beyond Snowflake and is limited by token lifetime and the permissions of the modified identity.

The affected libraries are all Snowflake client drivers for mainstream languages: the .NET, Python, Go, JDBC, Libsnowflakeclient, Node.js, ODBC, and PHP PDO drivers. The CVE description does not list the patched version numbers, so the user should consult the product release notes to identify which driver releases address the issue. All versions prior to the fix are vulnerable.

The vulnerability scores a CVSS of 8.2, indicating a high impact. The EPSS score is not provided, and it is not listed in the CISA KEV catalog, so there is no evidence yet of widespread exploitation. The exploit requires an attacker to influence the driver’s connection configuration or supply a crafted connection string. If an application allows an untrusted user to specify or alter the connection string, the attacker can trigger the vulnerability. Once exploited, the attacker can obtain a Snowflake access token that can be replayed or can acquire an Azure Managed Identity token for other services. Therefore, the risk is significant for organizations that use workload identity authentication and have drivers exposed to untrusted configuration inputs.