CVE-2026-19594

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

snowflake.core · PyPI

https://pypi.org/project/snowflake.core/1.13.0/

Vendor Advisories for CVE-2026-19594(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:02 UTCGHSA enrichment
  3. 2026-08-20 07:48 UTCGHSA enrichment
  4. 2026-08-19 18:37 UTCEG score recompute
  5. 2026-08-19 18:37 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 04:29 UTCGHSA enrichment
  8. 2026-08-18 15:13 UTCEG score recompute
  9. 2026-08-18 15:13 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 01:33 UTCEG score recompute
  12. 2026-08-18 01:33 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 12:22 UTCGHSA enrichment
  15. 2026-08-16 23:09 UTCEG score recompute
  16. 2026-08-16 23:09 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 09:58 UTCEG score recompute
  19. 2026-08-16 09:58 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 20:47 UTCGHSA enrichment
  22. 2026-08-15 07:36 UTCEG score recompute
  23. 2026-08-15 07:36 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 18:25 UTCGHSA enrichment
Show 15 more
  1. 2026-08-14 05:14 UTCEG score recompute
  2. 2026-08-14 05:14 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 16:02 UTCGHSA enrichment
  5. 2026-08-13 02:48 UTCEG score recompute
  6. 2026-08-13 02:48 UTCGHSA enrichment
  7. 2026-08-12 13:50 UTCEPSS rescore
  8. 2026-08-12 13:37 UTCEG score recompute
  9. 2026-08-12 13:37 UTCGHSA enrichment
  10. 2026-08-12 12:55 UTCEG score recompute
  11. 2026-08-12 12:55 UTCGHSA enrichment
  12. 2026-08-12 06:31 UTCEG score recompute
  13. 2026-08-12 06:31 UTCGHSA enrichment
  14. 2026-08-12 05:34 UTCEG score recompute
  15. 2026-08-12 05:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19594?
CVE-2026-19594 is a high vulnerability published on August 12, 2026. 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…
When was CVE-2026-19594 disclosed?
CVE-2026-19594 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19594 actively exploited?
CVE-2026-19594 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.1% of all scored CVEs.
What is the CVSS score of CVE-2026-19594?
CVE-2026-19594 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-19594?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19594, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19594

Explore →

Is Your Infrastructure Affected by CVE-2026-19594?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs