CVE intelligence and bounded remediation

CVE-2026-15736 — Snowflake SQLAlchemy security vulnerability

High CVSS 8.3

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, pote…

Severity
High
CVSS
8.3 (3.1)
Published
2026-07-14
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-73, CWE-89

Affected products

No browser-safe affected-product rows are available.

Matched remediation archetype

SQL and data-query injection

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace request, message, file, and stored values into SQL, ORM query fragments, filters, sort expressions, and other data-query languages.
  • Inventory database roles, reachable schemas, multi-tenant boundaries, and whether stacked or administrative operations are enabled.
  • Check both direct queries and second-order use of previously stored values.

Remediate safely

  • Use parameterized queries or safe query builders for all values; map identifiers and operators through explicit allowlists.
  • Remove raw query concatenation and give the application account only the tables and operations it requires.
  • Update affected data-access components and add regression tests for query structure preservation with inert edge-case inputs.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.