CVE-2018-17190

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2018-11-21. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 9%CVSS: 9.8Exploit: NoneExposed: 0

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

In all versions of Apache Spark, its standalone resource manager accepts code to execute on a 'master' host, that then runs that code on 'worker' hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
94.5%
KEV
Not listed

Published

November 19, 2018

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated May 28, 2026
No patch confirmed yet.
generic

Apache: Multiple vulnerabilities (GLSA 201903-21) — Gentoo security

https://security.gentoo.org/glsa/201903-21
generic
https://lists.apache.org/thread.html/341c3187f15cdb0d353261d2bfecf2324d56cb7db1339bfc7b30f6e5%40%3Cdev.spark.apache.org%3E
generic
http://www.securityfocus.com/bid/105976

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
mavenorg.apache.spark:spark-core_2.10—ghsa
mavenorg.apache.spark:spark-core_2.11—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.apache.spark:spark-core_2.100.9.0-incubating ... 2.2.3 (34 versions)——
org.apache.spark:spark-core_2.111.2.0 ... 2.4.8 (40 versions)——

Data Freshness Timeline

(refreshed 9× in last 7d / 44× 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-07-12 05:43 UTCEPSS rescore
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-09 19:06 UTCEPSS rescore
  4. 2026-07-08 15:11 UTCEPSS rescore
  5. 2026-07-07 13:42 UTCEPSS rescore
  6. 2026-07-07 13:42 UTCEPSS rescore
  7. 2026-07-06 16:24 UTCEPSS rescore
  8. 2026-07-06 16:24 UTCEPSS rescore
  9. 2026-07-06 02:20 UTCEPSS rescore
  10. 2026-07-05 02:27 UTCEPSS rescore
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-02 16:54 UTCEPSS rescore
  13. 2026-07-01 15:03 UTCEPSS rescore
  14. 2026-07-01 15:03 UTCEPSS rescore
  15. 2026-06-30 23:19 UTCEPSS rescore
  16. 2026-06-30 23:19 UTCEPSS rescore
  17. 2026-06-29 14:03 UTCEPSS rescore
  18. 2026-06-28 14:04 UTCEPSS rescore
  19. 2026-06-28 04:53 UTCEPSS rescore
  20. 2026-06-28 04:53 UTCEPSS rescore
  21. 2026-06-27 03:06 UTCEPSS rescore
  22. 2026-06-25 13:47 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-24 14:02 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 52 more
  1. 2026-06-23 21:30 UTCEPSS rescore
  2. 2026-06-22 14:23 UTCEPSS rescore
  3. 2026-06-21 14:54 UTCEPSS rescore
  4. 2026-06-21 14:54 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-19 19:23 UTCEPSS rescore
  8. 2026-06-18 17:50 UTCEPSS rescore
  9. 2026-06-18 17:50 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-16 17:50 UTCEPSS rescore
  14. 2026-06-15 17:45 UTCEPSS rescore
  15. 2026-06-14 23:14 UTCEPSS rescore
  16. 2026-06-14 23:14 UTCEPSS rescore
  17. 2026-06-13 22:58 UTCEPSS rescore
  18. 2026-06-13 22:58 UTCEPSS rescore
  19. 2026-06-12 23:09 UTCEPSS rescore
  20. 2026-06-11 13:57 UTCEPSS rescore
  21. 2026-06-10 22:16 UTCEPSS rescore
  22. 2026-06-10 13:19 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-08 14:14 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
  26. 2026-06-07 15:22 UTCEPSS rescore
  27. 2026-06-06 13:45 UTCEPSS rescore
  28. 2026-06-06 13:45 UTCEPSS rescore
  29. 2026-06-05 22:45 UTCEPSS rescore
  30. 2026-06-05 22:44 UTCEPSS rescore
  31. 2026-06-05 06:08 UTCEPSS rescore
  32. 2026-06-05 06:08 UTCEPSS rescore
  33. 2026-06-04 13:10 UTCEPSS rescore
  34. 2026-06-04 13:10 UTCEPSS rescore
  35. 2026-06-02 20:11 UTCEPSS rescore
  36. 2026-06-02 20:11 UTCEPSS rescore
  37. 2026-06-01 13:49 UTCEPSS rescore
  38. 2026-05-31 22:29 UTCEPSS rescore
  39. 2026-05-31 22:28 UTCEPSS rescore
  40. 2026-05-31 00:14 UTCEPSS rescore
  41. 2026-05-31 00:14 UTCEPSS rescore
  42. 2026-05-29 13:41 UTCEPSS rescore
  43. 2026-05-28 13:42 UTCEPSS rescore
  44. 2026-05-28 13:42 UTCEPSS rescore
  45. 2026-05-28 01:00 UTCEG score recompute
  46. 2026-05-28 01:00 UTCGHSA enrichment
  47. 2026-05-27 13:38 UTCEPSS rescore
  48. 2026-05-27 13:38 UTCEPSS rescore
  49. 2026-05-26 13:42 UTCEPSS rescore
  50. 2026-05-26 13:42 UTCEPSS rescore
  51. 2026-05-26 07:17 UTCEPSS rescore
  52. 2026-05-26 07:17 UTCEPSS rescore

Related CVEs(same product)

Same product

2 shown

maven:org.apache.spark:spark-core_2.11

Frequently asked(5)

What is CVE-2018-17190?
CVE-2018-17190 is a critical vulnerability published on November 19, 2018. In all versions of Apache Spark, its standalone resource manager accepts code to execute on a 'master' host, that then runs that code on 'worker' hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code…
When was CVE-2018-17190 disclosed?
CVE-2018-17190 was first published in the National Vulnerability Database on November 19, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-17190 actively exploited?
CVE-2018-17190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-17190?
CVE-2018-17190 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-17190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-17190, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-17190

Explore →

Is Your Infrastructure Affected by CVE-2018-17190?

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

Start Free Scan →Browse All CVEs