CVE-2026-85528: Snowflake JDBC Driver auto-configuration account validation permits credential redirection
Improper input validation of the auto-configuration account identifier in Snowflake JDBC Driver versions 4.2.0 through 4.3.3 allowed a credential-bearing login request to be redirected to an attacker-selected HTTPS endpoint. An attacker able to control the account value could cause the driver to transmit a reusable login credential to a host of their choosing and replay it to obtain the privileges granted to that credential. Successful exploitation requires an application using jdbc:snowflake:auto with a connections.toml section that omits an explicit host and a lower-trust principal able to set the account value; ordinary JDBC URLs are unaffected. The fix is available in Snowflake JDBC Driver version 4.3.4. Users must manually upgrade.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Snowflake JDBC Driverto a version that resolves this vulnerability.Fixed in 4.3.4 - Operational
Manually upgrade Snowflake JDBC Driver from versions 4.2.0 through 4.3.3 to version 4.3.4.
Event History
Frequently Asked Questions
Which deployments are exposed?
Only applications using jdbc:snowflake:auto with a connections.toml section that does not specify an explicit host are affected. Ordinary JDBC URLs are unaffected.
What access does an attacker need to exploit this?
The attacker must be a lower-trust principal who can set the auto-configuration account value. They can use that control to redirect a credential-bearing login request to an HTTPS endpoint they select.
What is the impact if exploitation succeeds?
The redirected request can disclose a reusable login credential to the attacker. The attacker can replay that credential with the privileges granted to it.
How can the issue be remediated or mitigated?
Manually upgrade the Snowflake JDBC Driver to version 4.3.4. Until upgraded, avoid the affected auto-configuration condition by using an explicit host in the relevant connections.toml section and prevent lower-trust principals from setting the account value.