SQL Injection via unescaped DataFrame column names in Snowflake Connector for Python and Snowflake Connector for Python (Universal Core)
- Exploited
- No known exploitation
- Fix
- Fixed in 4.8.1, 5.2.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.8.1, 5.2.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 46/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
When identifier escaping is disabled through a non-default configuration, the write_pandas() data-loading functionality in the Snowflake Connector for Python and the Snowflake Connector for Python (Universal Core) did not escape DataFrame column names before including them in generated SQL, which could allow SQL injection. In both products, a crafted column name could have been used to chain additional SQL statements onto the generated statement, potentially allowing an attacker to read, modify, or delete other data accessible to the application's Snowflake role. Exploitation required an application to pass attacker controlled column names into this functionality. The fix is available in Snowflake Connector for Python version 4.8.1 and Snowflake Connector for Python (Universal Core) version 5.2.0. Users must upgrade manually.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach20/20snowflake-connector-python: 25.6M downloads a week
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 91 if added to CISA KEV
- Would score about 86 if CISA's SSVC rates exploitation active
- Would score about 51 if advisories confirm default setups are exposed
Impact
- Widely used
snowflake-connector-python has 25.6m weekly downloads.Source: pypistats.org
337 packages depend on snowflake-connector-python.Source: deps.dev
What to do
Upgrade to a fixed version: 4.8.1, 5.2.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- snowflake-connector-pythonPyPI
From 2.3.4 · fixed in 4.8.1
- snowflake-connector-pythonPyPI
From 5.0.0b1 · fixed in 5.2.0
Evidence 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123859
Is CVE-2026-123859 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123859?
snowflake-connector-python (PyPI): from 2.3.4 before 4.8.1. snowflake-connector-python (PyPI): from 5.0.0b1 before 5.2.0.Source: cve.now feed data
How do I fix CVE-2026-123859?
Upgrade to a fixed version: 4.8.1, 5.2.0.Source: cve.now feed data