CVE-2026-123859 · Package
NO FIX YET · SEE WHAT TO DO
When identifier escaping is turned off through a non-default setting, the write_pandas() function in the Snowflake Connector for Python does not escape DataFrame column names before building SQL. A crafted column name can chain extra SQL statements, letting an attacker read, change or delete data the application's Snowflake role can reach.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications that call write_pandas() with identifier escaping disabled through a non-default configuration, and that let attacker-controlled column names reach it. The sources say exploitation required that an application pass attacker-controlled column names into this functionality. Applications with escaping at its default, or with only trusted column names, are not described as exposed.
Not affected if default-config, trusted-column-names
Who cares data-pipelines, python, snowflake
pip show snowflake-connector-python (or the Universal Core package used by the project)write_pandas() in the codebase and check whether identifier escaping is disabled in the connection or call settings4.8.15.2.0When 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.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.