CVE-2026-114456: Missing origin validation for the externalbrowser authenticator callback in multiple Snowflake client drivers
Multiple Snowflake client drivers implementing the authenticator=externalbrowser single sign-on flow could have allowed an attacker to interfere with a user's login attempt through weaknesses in the local loopback callback listener used to receive the identity provider's response. The listener reflected an arbitrary request's Origin header into its CORS response headers and accepted the first token-bearing request it received during the login window without verifying a CSRF state value bound to that specific login attempt. An attacker able to reach the listener during an active login might have leveraged this to submit a forged callback response, causing the authentication attempt to fail. The fix is available in Snowflake Connector for Python 4.8.0, Snowflake Go Driver v2.3.0, Snowflake JDBC Driver 4.4.0 (including the snowflake-jdbc-fips and snowflake-jdbc-thin artifacts), Snowflake Node.js Driver 3.4.0, Snowflake Connector for .NET 6.3.0, Snowflake ODBC Driver 4.0.0, Snowflake PHP PDO Driver 4.3.0, and libsnowflakeclient 2.11.1. Go v1 users must migrate to the latest major version of the module. Users must manually upgrade.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Snowflake Connector for Pythonto a version that resolves this vulnerability.Fixed in 4.8.0 - Upgrade
Upgrade
Snowflake Go Driverto a version that resolves this vulnerability.Fixed in v2.3.0 - Upgrade
Upgrade
Snowflake JDBC Driver, including snowflake-jdbc, snowflake-jdbc-fips, and snowflake-jdbc-thin artifactsto a version that resolves this vulnerability.Fixed in 4.4.0 - Upgrade
Upgrade
Snowflake Node.js Driverto a version that resolves this vulnerability.Fixed in 3.4.0 - Upgrade
Upgrade
Snowflake Connector for .NETto a version that resolves this vulnerability.Fixed in 6.3.0 - Upgrade
Upgrade
Snowflake ODBC Driverto a version that resolves this vulnerability.Fixed in 4.0.0 - Upgrade
Upgrade
Snowflake PHP PDO Driverto a version that resolves this vulnerability.Fixed in 4.3.0 - Upgrade
Upgrade
libsnowflakeclientto a version that resolves this vulnerability.Fixed in 2.11.1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Users of affected Snowflake client drivers who use the authenticator=externalbrowser single sign-on flow are exposed during an active login attempt. An attacker must be able to reach the local loopback callback listener while that login window is open.
What could an attacker do?
An attacker could submit a forged callback response before the legitimate identity-provider response is received, causing the authentication attempt to fail. The provided information describes an availability impact, not disclosure or modification of data.
Are upgrades required, and which versions contain the fix?
Users must manually upgrade. Fixed versions are Python Connector 4.8.0, Go Driver v2.3.0, JDBC Driver 4.4.0, Node.js Driver 3.4.0, .NET Connector 6.3.0, ODBC Driver 4.0.0, PHP PDO Driver 4.3.0, and libsnowflakeclient 2.11.1; JDBC 4.4.0 includes the snowflake-jdbc-fips and snowflake-jdbc-thin artifacts.
What should Go v1 users do?
Go v1 users must migrate to the latest major version of the module. The fix is available in Snowflake Go Driver v2.3.0.