CVE-2026-19594

The CVSS 8.1 rating for CVE-2026-19594 obscures a more nuanced risk profile. This isn't a straightforward injection flaw—it's a failure in how the snowflake-core library constructs REST requests when running under Snowflake's elevated-privilege execution contexts (EXECUTE AS OWNER, Streamlit apps, Native Apps). The dual mechanism matters: path traversal via '..' and parameter pollution via '&'/'#'/'=' both stem from the same root cause—treating user-supplied object names as safe when building HTTP requests. This isn't coincidence; it's a structural encoding failure that likely manifested across multiple endpoints, which explains the 'several additional security findings' language in the disclosure. The attack surface is narrower than generic CVSS scoring suggests. You need three prerequisites: access to a downstream application, the ability to control object-name strings within that application, and that application running under a Snowflake session with privileges高于 the attacker. But this narrowness is deceptive because the vulnerable patterns—Streamlit apps, Native Apps, stored procedures with EXECUTE AS OWNER—are exactly what Snowflake actively promotes as the standard way to build data applications. The vendor created these capabilities and simultaneously created the exploitation scenario when those capabilities mishandle untrusted input. For defenders, the priority is mapping which Streamlit apps, Native Apps, and stored procedures in your environment use EXECUTE AS OWNER or equivalent trust-elevation patterns, then verifying they run snowflake-core 1.13.0 or later. The manual upgrade requirement is a meaningful friction point—Python library dependencies often get pinned and forgotten, and unlike auto-updated services, this fix requires conscious deployment. Assume a significant population of production applications remain vulnerable for weeks to months after disclosure. Hunt retrospectively for anomalous '..' sequences or query parameter mutations in Snowflake query logs as indicators of exploitation attempts. The deeper concern is the pattern itself. This vulnerability shares genetic sequence with AWS Lambda confused-deputy issues (2019), GCP service account impersonation vectors, and Azure managed identity escalations. Cloud platforms consistently create high-privilege execution contexts for developer convenience, and those contexts become attack surfaces when untrusted input reaches them. Snowflake's implementation is the latest expression—not because the industry forgot, but because the specific lessons about how this manifests in Python REST clients, free-form name interpolation, and EXECUTE AS OWNER contexts aren't being systematically propagated across engineering organizations. Expect this genotype to recur in other platform APIs.

Reviewed through automated stages and approved by a human before publication.