Signal is active with 1 mentions in latest observed window
Immediate actions
Patch affected systems immediately
Recommended action window: Monitor and triage in normal cycle
NVD description
Insufficient input sanitization in Snowflake Python API (`snowflake.core`) versions prior to 1.13.0 allowed confused-deputy privilege escalation through two related weaknesses: path traversal (CWE-22) via unencoded `..` identifier path segments, and HTTP parameter pollution (CWE-141) via unencoded `&`/`#`/`=` characters in query string values. An attacker with access to a downstream application built on snowflake.core could exploit the path traversal by supplying `..` as an object name, causing `snowflake.core` to issue REST requests against a parent resource or exploit the parameter pollution by injecting `&`/`#`/`=` into a free-form name field to override constraints on swap, clone, or rename operations — all executed under the application's privileged session. Successful exploitation requires the attacker to control an identifier or object-name string in an application built on snowflake.core that passes it to `snowflake.core` under a higher-privileged Snowflake session (e.g., an EXECUTE AS OWNER stored procedure, Streamlit app, or Native App). The fix is available in Snowflake Python API version 1.13.0, which also addresses several additional security findings. Users must manually upgrade.
⚠️ Vulnerabilidad en Componente de Python
❗ CVE-2026-19594
➡️ Más info: https://www.cert.gov.py/vulnerabilidad-en-productos-python-3/ https://t.co/GGWlFcFSNz
Post summary
The tweet announces a vulnerability (CVE-2026-19594) in a Python component but offers no technical specifics, proof‑of‑concept, or patch information.
🚨High - Snowflake Python API Confused-Deputy Privilege Escalation (CVE-2026-19594)
Snowflake's official Python API (snowflake.core) before 1.13.0 insufficiently sanitizes identifiers and query values. An attacker who controls an object-name string in a downstream app can supply ".." for path traversal (issuing REST calls against a parent resource) or inject &, #, or = for HTTP parameter pollution to override constraints on swap, clone, or rename operations.
Because the app relays this input under its own higher-privileged Snowflake session, for example, an EXECUTE AS OWNER stored procedure, Streamlit app, or Native App, the actions run with privileges the attacker doesn't have. Impact is to integrity and availability. CVSS 8.1.
👉Upgrade snowflake.core to 1.13.0 (manual upgrade required).
Post summary
The tweet announces a high‑impact privilege escalation flaw in Snowflake's Python API, provides technical details about how it can be exploited, and advises users to upgrade to version 1.13.0.