CVE-2026-15736

Multiple SQL/DDL Injection and Arbitrary File Read Vulnerabilities in snowflake-sqlalchemy

Published Jul 14, 2026 CVSS 3.1 · 8.3 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Snowflake SQLAlchemy versions before 1.11.0 expose multiple injection flaws: the library does not correctly sanitize user‑supplied column identifiers used in MERGE statements, it improperly renders bound parameters when constructing Snowflake‑specific CREATE TABLE queries, and it forwards connection configuration parameters in a way that permits reading local files. These weaknesses can allow an attacker to inject arbitrary SQL, alter data, or exfiltrate information that the application’s database role can access, and to read sensitive files from the application host and send them to an external endpoint.

Affected Systems

The vulnerability affects installations of the Snowflake SQLAlchemy Python package older than 1.11.0. Any application that integrates this library—particularly dynamic upsert endpoints, table‑creation APIs, or connection string handling routines that accept user input—is potentially exposed.

Risk and Exploitability

The CVSS score is 8.3, indicating high severity, while the EPSS score is below 1%, suggesting a very low probability of exploitation in the wild. The vulnerability is not listed in CISA KEV. Attackers would need to supply crafted request fields or connection parameters to an application that uses the vulnerable package, typically via standard web or API calls, and would not require privileges beyond those granted to the application’s database role.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Snowflake SQLAlchemy to version 1.11.0 or newer
  • Validate or sanitize all user‑supplied column identifiers, table names, and bound parameters before invoking MERGE or CREATE TABLE calls
  • Restrict or sanitize user‑controlled connection configuration values and enforce strict input validation on file paths to prevent local file reads

Generated by OpenCVE AI on July 31, 2026 at 10:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-8g6f-qw9x-4q6q Snowflake SQLAlchemy affected by SQL injection and local file disclosure vulnerabilities
History
Type Values Removed Values Added
First Time appeared Snowflake
Snowflake snowflake Sqlalchemy
Vendors & Products Snowflake
Snowflake snowflake Sqlalchemy
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Multiple SQL/DDL Injection and Arbitrary File Read Vulnerabilities in snowflake-sqlalchemy
Weaknesses CWE-73
CWE-89
References
Metrics cvssV3_1

{'score': 8.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L'}

Weaknesses
  • CWE-73

    External Control of File Name or Path

  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
SNOWFLAKE
Published
Updated
Jul 14, 2026, 3:14 PM
Reserved
Jul 14, 2026, 2:01 PM
Status
Awaiting Analysis
Published
Jul 14, 2026, 3:17 PM
Modified
Oct 24, 2026, 9:10 PM