Severity by source
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
Config-modification access needed (PR:L/AC:H); scope change justified by Azure token exfiltration extending to non-Snowflake resources; no availability impact.
Primary rating from Vendor (SNOWFLAKE).
CVSS VectorVendor: SNOWFLAKE
Lifecycle Timeline
5DescriptionCVE.org
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.
AnalysisAI
Workload Identity Federation authentication in all major Snowflake client drivers transmits cloud attestation tokens to the configured host without first verifying that host is a recognized Snowflake endpoint, enabling token exfiltration and replay. An attacker who can modify connection configuration redirects the driver to an attacker-controlled server, which receives a freshly minted cloud workload-identity token that can be replayed against real Snowflake accounts for the token's remaining lifetime. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires three concurrent conditions: (1) the application must be configured to use the WORKLOAD_IDENTITY authenticator - this is an explicit non-default configuration choice, not the standard password or key-pair auth; (2) the workload must already possess an ambient cloud identity, meaning it runs on a cloud compute instance with an attached AWS IAM role, Azure Managed Identity, or GCP service account; and (3) the attacker must have write access to the connection configuration - specifically the ability to override the Snowflake host setting via connection string parameters, environment variables, or configuration files accessible to the application process. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.2 vector (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N) accurately reflects the compound prerequisites: low-privilege access to modify connection configuration and an environment already configured for WORKLOAD_IDENTITY with an ambient cloud identity. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patches are available for all eight drivers, all published September 3, 2026; users must manually upgrade as no auto-update mechanism exists. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, update all Snowflake client drivers to patched versions released September 3, 2026 across all eight affected packages and verify connectivity to legitimate Snowflake endpoints. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Improper TLS hostname verification in the Snowflake Connector for Python (versions before 4.7.1) lets an on-path attacke
Improper OCSP response validation across the Snowflake Python, Go, JDBC, and Node.js drivers allowed a revoked TLS certi
Sensitive credential material - including authentication tokens, query-result encryption keys, pre-signed cloud-storage
Same weakness CWE-522 – Insufficiently Protected Credentials
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-72877
GHSA-fhj9-24fm-m53p