Skip to content
Fencer Intel
medium 6.5

CVE-2026-114456 json

Missing origin validation for the externalbrowser authenticator callback in multiple Snowflake client drivers

published 5d ago modified 3d ago also EUVD-2026-116883

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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.

Patch / fix

  • Snowflake Snowflake Connector for Python 4.8.0
  • Snowflake Snowflake Go Driver 2.3.0
  • Snowflake Snowflake JDBC Driver 4.4.0
  • Snowflake Snowflake JDBC Driver (FIPS) 4.4.0
  • Snowflake Snowflake JDBC Driver (Thin) 4.4.0
  • Snowflake Snowflake Node.js Driver 3.4.0
  • Snowflake Snowflake Connector for .NET 6.3.0
  • Snowflake Snowflake ODBC Driver 4.0.0
  • Snowflake Snowflake PHP PDO Driver 4.3.0
  • Snowflake Snowflake Libsnowflakeclient 2.11.1

Is CVE-2026-114456 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5d ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected products

  • Snowflake Snowflake Connector for Python
  • Snowflake Snowflake Go Driver
  • Snowflake Snowflake JDBC Driver
  • Snowflake Snowflake JDBC Driver (FIPS)
  • Snowflake Snowflake JDBC Driver (Thin)
  • Snowflake Snowflake Node.js Driver
  • Snowflake Snowflake Connector for .NET
  • Snowflake Snowflake ODBC Driver
  • Snowflake Snowflake PHP PDO Driver
  • Snowflake Snowflake Libsnowflakeclient

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.