Snowflake SQLAlchemy: SQL injection
High8.3CVE-2026-15736 · Published Jul 14, 2026 · updated Jul 15, 2026
Snowflake SQLAlchemy versions prior to 1.11.0 contain several security vulnerabilities, including: Improper handling of user-supplied column identifiers in merge operations could allow SQL injection through attacker-controlled input keys. An attacker may be able to exploit this through request field names in a dynamic upsert endpoint, potentially enabling read access to data visible to the application's database role or modification of values within the same MERGE statement. Improper literal rendering of bound parameters when building certain Snowflake-specific table creation queries could allow SQL injection. An attacker may be able to exploit this by supplying a crafted string to any application endpoint that passes user-controlled data through the affected query-building API, potentially causing arbitrary data exfiltration within the scope of the connection role. Improper forwarding of connection configuration parameters could allow an attacker to cause the library to read arbitrary local files and transmit their contents to an attacker-controlled endpoint. An attacker may be able to exploit this in deployment environments that accept user-controlled connection parameters, poten...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| Snowflake SQLAlchemy Product | >= 1.1.6, < 1.11.0 | 1.11.0 |
Details and references
Snowflake SQLAlchemy versions prior to 1.11.0 contain several security vulnerabilities, including: Improper handling of user-supplied column identifiers in merge operations could allow SQL injection through attacker-controlled input keys. An attacker may be able to exploit this through request field names in a dynamic upsert endpoint, potentially enabling read access to data visible to the application's database role or modification of values within the same MERGE statement. Improper literal rendering of bound parameters when building certain Snowflake-specific table creation queries could allow SQL injection. An attacker may be able to exploit this by supplying a crafted string to any application endpoint that passes user-controlled data through the affected query-building API, potentially causing arbitrary data exfiltration within the scope of the connection role. Improper forwarding of connection configuration parameters could allow an attacker to cause the library to read arbitrary local files and transmit their contents to an attacker-controlled endpoint. An attacker may be able to exploit this in deployment environments that accept user-controlled connection parameters, potentially exposing sensitive files accessible to the application process. The fix is available in Snowflake SQLAlchemy version 1.11.0. Users must manually upgrade.
More Snowflake advisories
All Snowflake| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Aug 12 | Snowflake Python APIs: privilege escalation | High8.1 | 1.13.0 |
| Jul 24 | Snowflake ODBC Driver: remote code execution | High8.8 | Snowflake libsnowflakeclient 2.9.2+2 more |
| Jul 16 | Snowflake Connector for Python: improper TLS hostname check | Critical9.2 | 3.18.1+1 more |
| Jul 14 | Snowflake Spark Connector: SQL injection | Critical9.2 | 3.2.1 |
| Jul 8 | Snowflake Snowpark Python SDK: SQL injection | Critical9.6 | 1.53.0 |
| Jul 8 | Terraform Provider for Snowflake: SQL injection | High8.8 | 2.18.0 |