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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "8.1",
  "pubDate": "2026-08-12T06:21:57.223Z",
  "pubdate": "2026-08-12T06:21:57.223Z",
  "executiveSummary": "An insufficient input sanitization vulnerability exists in the Snowflake Python API (snowflake.core) in versions prior to 1.13.0, enabling confused-deputy privilege escalation.\nThe vulnerability stems from path traversal via unencoded identifier path segments and HTTP parameter pollution via unencoded characters in query string values.\nAn attacker capable of controlling identifier or object-name strings in downstream applications can exploit these weaknesses.\nSuccessful exploitation allows attackers to cause the snowflake.core component to issue REST requests against parent resources or override constraints on swap, clone, or rename operations.\nOperations are executed under the higher-privileged session of the application, such as an EXECUTE AS OWNER stored procedure, Streamlit app, or Native App.\nImpact includes unauthorized resource manipulation and privilege escalation within the context of the privileged Snowflake session.\nRemediation requires upgrading the Snowflake Python API to version 1.13.0 or later.",
  "technicalDetails": "The vulnerability involves two related weaknesses within the snowflake.core component of the Snowflake Python API in versions prior to 1.13.0: path traversal (CWE-22) and HTTP parameter pollution (CWE-141).\nThe root cause is insufficient input sanitization of user-supplied strings used to construct REST API requests. Specifically, path traversal is facilitated by unencoded '..' identifier path segments, while HTTP parameter pollution is caused by unencoded '&', '#', and '=' characters in query string values.\nThe vulnerable component is the snowflake.core library, which fails to properly validate or sanitize identifiers and free-form name fields before incorporating them into REST requests.\nExploitation requires an attacker to have control over an identifier or object-name string within a downstream application built on snowflake.core. This string must be passed to snowflake.core under a higher-privileged Snowflake session, such as an EXECUTE AS OWNER stored procedure, a Streamlit application, or a Native App.\nDuring path traversal exploitation, supplying '..' as an object name forces snowflake.core to issue REST requests targeting a parent resource, thereby breaking out of the intended resource hierarchy.\nDuring parameter pollution exploitation, injecting control characters such as '&', '#', and '=' into free-form name fields allows the attacker to manipulate query parameters, overriding constraints on swap, clone, or rename operations.\nBecause the downstream application executes these operations under a privileged session, the resulting unauthorized REST requests and parameter manipulations are performed with elevated privileges, leading to confused-deputy privilege escalation.\nNo network exposure of the vulnerability exists independently of the downstream application; exploitation depends entirely on the application accepting untrusted input and passing it to the vulnerable snowflake.core APIs."
}