CVE-2023-32007

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 76% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 76%
CISA-KEV: Not listedEPSS: 76%CVSS: 8.8Exploit: NoneExposed: 0

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

UNSUPPORTED WHEN ASSIGNED The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as. This issue was disclosed earlier as CVE-2022-33891, but incorrectly claimed version 3.1.3 (which has since gone EOL) would not be affected.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Users are recommended to upgrade to a supported version of Apache Spark, such as version 3.4.0.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
71(Track)
EG Risk 71/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
Severity90% × 45%
Exploitation76% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.5%
KEV
Not listed

Published

May 2, 2023

Last Modified

February 13, 2025

References (8)

Affected Packages

(2 across 2 ecosystems)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.spark:spark-parent_2.123.1.1, 3.1.2, 3.1.3, 3.2.0, 3.2.13.2.2—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pyspark2.1.1 ... 3.2.1 (30 versions)3.2.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× 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-07-23 02:22 UTCEG score recompute▲ 0.20
  2. 2026-07-22 23:09 UTCEG score recompute▼ 0.20
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-20 17:06 UTCEPSS rescore
  7. 2026-07-19 14:29 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-16 17:01 UTCEPSS rescore
  14. 2026-07-16 17:01 UTCEPSS rescore
  15. 2026-07-15 21:49 UTCOSV refresh
  16. 2026-07-15 16:56 UTCEPSS rescore
  17. 2026-07-15 16:56 UTCEPSS rescore
  18. 2026-07-15 01:58 UTCEPSS rescore
  19. 2026-07-15 01:58 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-13 06:11 UTCEPSS rescore
  22. 2026-07-11 08:25 UTCEPSS rescore
  23. 2026-07-11 08:25 UTCEPSS rescore
  24. 2026-07-08 15:13 UTCEPSS rescore
  25. 2026-07-06 16:26 UTCEPSS rescore
Show 39 more
  1. 2026-07-06 16:26 UTCEPSS rescore
  2. 2026-07-05 02:28 UTCEPSS rescore
  3. 2026-07-02 16:59 UTCEPSS rescore
  4. 2026-07-01 15:04 UTCEPSS rescore
  5. 2026-06-30 23:21 UTCEPSS rescore
  6. 2026-06-30 23:21 UTCEPSS rescore
  7. 2026-06-29 14:05 UTCEPSS rescore
  8. 2026-06-28 04:54 UTCEPSS rescore
  9. 2026-06-27 22:04 UTCOSV refresh
  10. 2026-06-25 13:48 UTCEPSS rescore
  11. 2026-06-25 13:48 UTCEPSS rescore
  12. 2026-06-24 14:03 UTCEPSS rescore
  13. 2026-06-24 14:03 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-23 21:31 UTCEPSS rescore
  16. 2026-06-21 01:58 UTCEPSS rescore
  17. 2026-06-21 01:58 UTCEPSS rescore
  18. 2026-06-18 17:51 UTCEPSS rescore
  19. 2026-06-18 17:51 UTCEPSS rescore
  20. 2026-06-16 17:51 UTCEPSS rescore
  21. 2026-06-16 17:51 UTCEPSS rescore
  22. 2026-06-15 17:47 UTCEPSS rescore
  23. 2026-06-12 23:10 UTCEPSS rescore
  24. 2026-06-10 22:17 UTCEPSS rescore
  25. 2026-06-10 09:17 UTCOSV refresh
  26. 2026-06-01 13:51 UTCEPSS rescore
  27. 2026-05-31 22:29 UTCEPSS rescore
  28. 2026-05-31 22:29 UTCEPSS rescore
  29. 2026-05-31 22:29 UTCEPSS rescore
  30. 2026-05-31 00:15 UTCEPSS rescore
  31. 2026-05-31 00:15 UTCEPSS rescore
  32. 2026-05-28 13:43 UTCEPSS rescore
  33. 2026-05-28 13:43 UTCEPSS rescore
  34. 2026-05-27 13:39 UTCEPSS rescore
  35. 2026-05-27 13:39 UTCEPSS rescore
  36. 2026-05-26 07:18 UTCEPSS rescore
  37. 2026-05-26 07:18 UTCEPSS rescore
  38. 2026-05-26 07:17 UTCEPSS rescore
  39. 2026-05-25 02:05 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-32007?
CVE-2023-32007 is a high vulnerability published on May 2, 2023. UNSUPPORTED WHEN ASSIGNED The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in…
When was CVE-2023-32007 disclosed?
CVE-2023-32007 was first published in the National Vulnerability Database on May 2, 2023, with the most recent update on February 13, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-32007 actively exploited?
CVE-2023-32007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-32007?
CVE-2023-32007 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2023-32007?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-32007, 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-2023-32007

Explore →

Is Your Infrastructure Affected by CVE-2023-32007?

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

Start Free Scan →Browse All CVEs