CVE-2026-15183

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (22nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
9.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.2Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (SNOWFLAKE) lists Snowflake Spark Connector versions 0.1.0 up to but not including 3.2.1 as affected. No release containing a fix is confirmed on record.

Multiple input validation vulnerabilities in the Snowflake Spark Connector (spark-snowflake) versions prior to 3.2.1 can allow attackers to exfiltrate OAuth client credentials, execute arbitrary SQL with the connector's Snowflake role, or redirect COPY operations to attacker-controlled storage. An attacker could exploit these vulnerabilities by supplying a crafted OAuth token request URL, placing malicious files in an ingestion pipeline, injecting SQL via staging options in a shared Spark environment , or issuing runtime SET commands in a shared Spark-SQL session to inject arbitrary SQL into the SnowflakeFallbackCatalog's option map, which executes under the cluster admin's JDBC credentials. Successful exploitation may result in credential theft, unauthorized access to Snowflake account data, or privilege escalation within connected infrastructure.

CVSS v3
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

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 (value × EchelonGraph’s weight)
Severity92% × 45%
The EG Score, 9.2 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
No fix on record yet.
Web page

Snowflake Connector for Spark release notes for 2026 | Snowflake Documentation

https://docs.snowflake.com/en/release-notes/clients-drivers/spark-connector-2026

Vendor Advisories for CVE-2026-15183(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 353 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 253 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 02:50 UTCEG score recompute
  2. 2026-10-14 02:49 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-12 22:56 UTCEG score recompute
  5. 2026-10-12 22:56 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-12 16:32 UTCEG score recompute
  8. 2026-10-12 09:40 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  9. 2026-10-11 20:10 UTCEG score recompute
  10. 2026-10-11 17:22 UTCEG score recompute
  11. 2026-10-11 14:55 UTCEG score recompute
  12. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-10-01 13:28 UTCEG score recompute
  23. 2026-10-01 13:28 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  24. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 75 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-09-28 13:36 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  3. 2026-09-28 09:24 UTCEG score recompute
  4. 2026-09-28 09:24 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  5. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-09-24 09:56 UTCEG score recompute
  8. 2026-09-24 09:56 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  9. 2026-09-23 08:13 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  10. 2026-09-23 04:00 UTCEG score recompute
  11. 2026-09-23 04:00 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  12. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-09-18 10:05 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  14. 2026-09-18 04:57 UTCEG score recompute
  15. 2026-09-18 04:57 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  16. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-09-14 07:54 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  19. 2026-09-14 03:41 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  20. 2026-09-13 23:29 UTCEG score recompute
  21. 2026-09-13 23:29 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  22. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-09-13 16:28 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  24. 2026-09-13 12:08 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  25. 2026-09-13 07:56 UTCEG score recompute
  26. 2026-09-13 07:56 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  27. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  28. 2026-09-12 13:24 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  29. 2026-09-12 07:28 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  30. 2026-09-12 01:47 UTCEG score recompute
  31. 2026-09-12 01:47 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  32. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-09-08 01:49 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  37. 2026-09-06 13:47 UTCEG score recompute
  38. 2026-09-06 13:47 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  39. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-09-06 01:35 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  41. 2026-09-05 21:20 UTCEG score recompute
  42. 2026-09-05 21:20 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  43. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  44. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  45. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  47. 2026-08-31 05:48 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  48. 2026-08-31 00:49 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  49. 2026-08-30 20:36 UTCEG score recompute
  50. 2026-08-30 20:36 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  51. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  52. 2026-08-30 16:24 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  53. 2026-08-30 10:59 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  54. 2026-08-30 05:25 UTCEG score recompute
  55. 2026-08-30 05:25 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  56. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  57. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-08-28 02:29 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  59. 2026-08-27 21:34 UTCEG score recompute
  60. 2026-08-27 21:34 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  61. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-08-27 13:54 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  63. 2026-08-27 05:09 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  64. 2026-08-27 00:01 UTCEG score recompute
  65. 2026-08-27 00:01 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  66. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-08-26 12:17 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  68. 2026-08-26 07:34 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  69. 2026-08-26 01:55 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  70. 2026-08-25 19:14 UTCEG score recompute
  71. 2026-08-25 19:14 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  72. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  73. 2026-08-25 13:28 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  74. 2026-08-25 09:15 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL
  75. 2026-08-25 04:20 UTCGHSA enrichmentGHSA-33r9-fx8q-w69h · GitHub severity CRITICAL

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15183?
CVE-2026-15183 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Multiple input validation vulnerabilities in the Snowflake Spark Connector (spark-snowflake) versions prior to 3.2.1 can allow attackers to exfiltrate OAuth client credentials, execute arbitrary SQL with the connector's Snowflake role, or redirect COPY operations to attacker-controlled storage. An…
When was the CVE record for CVE-2026-15183 published?
The CVE record for CVE-2026-15183 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-15183 actively exploited?
CVE-2026-15183 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15183?
CVE-2026-15183 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15183?
No fix for CVE-2026-15183 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (SNOWFLAKE) lists Snowflake Spark Connector versions 0.1.0 up to but not including 3.2.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-15183 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15183?

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

Book a Demo →Browse All CVEs