CVE-2026-15736
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSnowflake 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSnowflake SQLAlchemy versions before 1.11.0 contain three distinct vulnerabilities: (1) SQL injection via improper handling of user-supplied column identifiers in MERGE operations exploitable through dynamic upsert endpoints, allowing data read/modification within the application's role scope; (2) SQL injection via improper literal rendering of bound parameters in Snowflake-specific table creation queries enabling arbitrary data exfiltration; (3) arbitrary local file read via improper connection configuration parameter forwarding, allowing attackers to exfiltrate files accessible to the application process to attacker-controlled endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Snowflake SQLAlchemy versionRun `pip show snowflake-sqlalchemy` or import snowflake_sqlalchemy; print(snowflake_sqlalchemy.__version__)Affected if Version is lower than 1.11.0 or version cannot be determined (package not installed)
-
Identify merge operations using dynamic column identifiersSearch codebase for usage of `merge()` method or upsert operations where column names are derived from user input, request parameters, or dynamically constructed dictionariesAffected if Application performs merge/upsert operations with user-supplied column names and uses snowflake-sqlalchemy < 1.11.0
-
Identify Snowflake table creation with dynamic literalsSearch for `CreateTable` or `Table(...).create()` calls in snowflake dialect where column definitions, constraints, or table options include user-supplied values rendered as literalsAffected if Application creates tables using Snowflake dialect with user-controlled values in table/column definitions and uses snowflake-sqlalchemy < 1.11.0
-
Check if connection parameters accept user inputReview application code that accepts connection parameters (host, account, warehouse, database, schema, or custom parameters) from user requests, APIs, or untrusted sourcesAffected if Connection parameters can be controlled by users or untrusted sources and application uses snowflake-sqlalchemy < 1.11.0
User is affected if snowflake-sqlchemy version is below 1.11.0 AND the application uses merge operations, table creation with dynamic values, or accepts user-controlled connection parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Snowflake SQLAlchemy library to version 1.11.0 or later; review and sanitize any user-controlled input passed to merge operations, table creation APIs, or connection configuration parameters in existing code.
Snowflake SQLAlchemy version 1.11.0
- Check the currently installed version of Snowflake SQLAlchemy by running: pip show snowflake-sqlalchemy
- Upgrade to version 1.11.0 or later using: pip install --upgrade snowflake-sqlalchemy>=1.11.0
- Verify the upgrade was successful by running: pip show snowflake-sqlalchemy and confirming the version number is 1.11.0 or higher
- Review application code that uses Snowflake SQLAlchemy to ensure compatibility with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15736 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15736 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data