CVE-2026-15736
SQL injection and local-file exfiltration in Snowflake SQLAlchemy (<1.11.0).
Is CVE-2026-15736 being exploited?
Not confirmed. CVE-2026-15736 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-15736?
CVE-2026-15736 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-15736?
Yes. A fix has been recorded for CVE-2026-15736. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15736 affect?
CVE-2026-15736 affects snowflake-sqlalchemy < 1.11.0, Python apps using snowflake-sqlalchemy, Applications performing dynamic MERGE/upsert to Snowflake. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15736?
Upgrade to snowflake-sqlalchemy 1.11.0 and sanitize/validate identifiers and connection params.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SQL injection via crafted identifiers/literals enables data read/modify; attacker-controlled connection params can force local file read and exfiltration.
Immediate action required
- affected>= 1.1.6 and < 1.11.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.