CVE-2026-114456 · Package
NO FIX YET · SEE WHAT TO DO
Several Snowflake client drivers using the externalbrowser single sign-on flow run a local loopback listener that accepts the first token-bearing request without checking a per-login CSRF state value. An attacker who can reach that listener during an active login can submit a forged callback and make the authentication attempt fail.
first public Nov 4, 2026 · 1 source
Is this in your stack? Find out in 2 minutes.
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Only systems that use a Snowflake client driver with the externalbrowser SSO login flow are exposed, and the attacker must be able to reach the local loopback listener during a login window. Services using key-pair, password, or OAuth authentication without externalbrowser are not described as affected by the sources.
Not affected if headless-service-accounts, no-externalbrowser-auth
Who cares dotnet, go, jdbc, node.js, odbc, php, python, snowflake
authenticator=externalbrowser in connection strings or driver config.pip show snowflake-connector-python, npm ls snowflake-sdk, the JDBC snowflake-jdbc artifact version, and libsnowflakeclient version.4.8.0v2.3.0 (Go v1 users must migrate to the latest major version of the module)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.
4.4.0 (including snowflake-jdbc-fips and snowflake-jdbc-thin)3.4.06.3.04.0.04.3.02.11.1This page as .md · .json · in your agent: get_signal("CVE-2026-114456") · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.