CVE-2026-15736

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. A secondary CVSS source baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
8.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity83% × 45%
The EG Score, 8.3 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jul 14, 2026
Patch available.
Web page

Releases · snowflakedb/snowflake-sqlalchemy · GitHub

https://github.com/snowflakedb/snowflake-sqlalchemy/releases

Vendor Advisories for CVE-2026-15736(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
snowflake-sqlalchemy1.1.10 ... 1.9.0 (48 versions)
  • 1.1.6 up to 1.11.0: fixed in 1.11.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 202 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-12 16:31 UTCEG score recompute
  4. 2026-10-11 20:09 UTCEG score recompute
  5. 2026-10-11 17:22 UTCEG score recompute
  6. 2026-10-11 14:55 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-10-01 13:26 UTCEG score recompute
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-09-28 09:23 UTCEG score recompute
  22. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-09-24 09:55 UTCEG score recompute
  25. 2026-09-23 03:57 UTCEG score recompute
Show 75 more
  1. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-09-18 04:55 UTCEG score recompute
  3. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-09-13 23:28 UTCEG score recompute
  6. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-09-13 07:55 UTCEG score recompute
  8. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-09-12 01:47 UTCEG score recompute
  10. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-09-08 01:47 UTCEG score recompute
  15. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-09-05 21:18 UTCEG score recompute
  18. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-08-31 05:44 UTCEG score recompute
  23. 2026-08-31 05:44 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-08-30 16:54 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  26. 2026-08-30 05:25 UTCEG score recompute
  27. 2026-08-30 05:25 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  28. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  29. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-08-28 02:28 UTCEG score recompute
  31. 2026-08-28 02:28 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  32. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  33. 2026-08-27 13:53 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  34. 2026-08-27 01:19 UTCEG score recompute
  35. 2026-08-27 01:19 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  36. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  37. 2026-08-26 13:48 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  38. 2026-08-26 01:51 UTCEG score recompute
  39. 2026-08-26 01:51 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  40. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  41. 2026-08-25 09:14 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  42. 2026-08-24 20:46 UTCEG score recompute
  43. 2026-08-24 20:46 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  44. 2026-08-24 09:16 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  45. 2026-08-23 21:18 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  46. 2026-08-23 09:48 UTCEG score recompute
  47. 2026-08-23 09:48 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  49. 2026-08-22 22:19 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  50. 2026-08-22 10:49 UTCEG score recompute
  51. 2026-08-22 10:49 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  52. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  53. 2026-08-21 23:19 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  54. 2026-08-21 11:48 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  55. 2026-08-20 23:46 UTCEG score recompute
  56. 2026-08-20 23:46 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  57. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  58. 2026-08-20 12:17 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  59. 2026-08-20 00:35 UTCEG score recompute
  60. 2026-08-20 00:35 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  61. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  62. 2026-08-19 09:47 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  63. 2026-08-18 22:18 UTCEG score recompute
  64. 2026-08-18 22:18 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  65. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  66. 2026-08-18 10:26 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  67. 2026-08-17 21:39 UTCEG score recompute
  68. 2026-08-17 21:39 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  69. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  70. 2026-08-17 05:53 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  71. 2026-08-16 18:10 UTCEG score recompute
  72. 2026-08-16 18:10 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3
  73. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  74. 2026-08-16 06:40 UTCEG score recompute
  75. 2026-08-16 06:40 UTCGHSA enrichmentGHSA-8g6f-qw9x-4q6q · GitHub severity HIGH · GitHub CVSS 8.3

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15736?
CVE-2026-15736 is a high-severity vulnerability; its CVE record was published on July 14, 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…
When was the CVE record for CVE-2026-15736 published?
The CVE record for CVE-2026-15736 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-15736 actively exploited?
CVE-2026-15736 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15736?
CVE-2026-15736 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15736?
A fix for CVE-2026-15736 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15736 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15736

Explore →

Is Your Infrastructure Affected by CVE-2026-15736?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs