CVE-2022-33891

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-03-07), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2022-0217 (ENISA EUVD) · GHSA-4x9r-j582-cgr8 (GitHub Security Advisories) · PYSEC-2022-236 (OSV.dev)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 93%CVSS: 8.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

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 affects Apache Spark versions 3.0.3 and earlier, versions 3.1.1 to 3.1.2, and versions 3.2.0 to 3.2.1.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
80
EG Risk 80/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (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: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
93%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.8 HIGH.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
93% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (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)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (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

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://lists.apache.org/thread/p847l3kopoo5bjtmxrcwk21xp6tjxqlc · https://nvd.nist.gov/vuln/detail/CVE-2022-33891

Published

July 18, 2022

Last Modified

October 23, 2025

Advisory Details (4)

Auto-updated Nov 9, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-33891
Web page

oss-security - CVE-2023-32007: Apache Spark: Shell command injection via Spark UI

http://www.openwall.com/lists/oss-security/2023/05/02/1

Vendor Advisories for CVE-2022-33891(1)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.apache.spark:spark-parent_2.12—ghsa
mavenorg.apache.spark:spark-parent_2.12 @ 3.2.2 (fixes >= 3.1.1, < 3.2.2)—ghsa
pippyspark @ 3.1.3 (fixes >= 0, < 3.1.3)—ghsa
pippyspark @ 3.2.2 (fixes >= 3.2.0, < 3.2.2)—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 2 ecosystems)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.spark:spark-parent_2.123.1.1, 3.1.2, 3.1.3, 3.2.0, 3.2.1
  • every version through 3.0.3: no fix on record
  • 3.1.1 up to 3.2.2: fixed in 3.2.2
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyspark2.1.1 ... 3.2.1 (29 versions)
  • every version up to 3.1.3: fixed in 3.1.3
  • 3.2.0 up to 3.2.2: fixed in 3.2.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 22× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 196 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:42 UTCEPSS rescoreEPSS 93% · 99th percentile
  2. 2026-11-13 06:26 UTCEchelonGraph re-scored
  3. 2026-11-13 06:26 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-11-12 05:05 UTCEchelonGraph re-scored
  5. 2026-11-12 05:05 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-11-11 16:32 UTCEPSS rescoreEPSS 93% · 99th percentile
  7. 2026-11-11 03:44 UTCEchelonGraph re-scored
  8. 2026-11-11 03:44 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-11-10 02:23 UTCEchelonGraph re-scored
  10. 2026-11-10 02:23 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-11-09 01:02 UTCEchelonGraph re-scored
  12. 2026-11-09 01:02 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-11-07 23:42 UTCEchelonGraph re-scored
  14. 2026-11-07 23:42 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-11-06 22:21 UTCEchelonGraph re-scored
  16. 2026-11-06 22:21 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-11-06 16:30 UTCEPSS rescoreEPSS 93% · 99th percentile
  18. 2026-11-05 20:55 UTCEchelonGraph re-scored
  19. 2026-11-05 20:55 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-11-04 19:35 UTCEchelonGraph re-scored
  21. 2026-11-04 19:35 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-11-04 16:30 UTCEPSS rescoreEPSS 93% · 99th percentile
  23. 2026-11-04 04:25 UTCOSV refresh
  24. 2026-11-03 18:14 UTCEchelonGraph re-scored
  25. 2026-11-03 18:14 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
Show 74 more
  1. 2026-11-02 16:52 UTCEchelonGraph re-scored
  2. 2026-11-02 16:52 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-01 15:31 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-11-01 08:26 UTCGHSA enrichmentGHSA-4x9r-j582-cgr8 · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-11-01 08:26 UTCEchelonGraph re-scored
  6. 2026-10-31 14:11 UTCEchelonGraph re-scored
  7. 2026-10-30 12:50 UTCEchelonGraph re-scored
  8. 2026-10-29 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  9. 2026-10-29 11:29 UTCEchelonGraph re-scored
  10. 2026-10-28 10:09 UTCEchelonGraph re-scored
  11. 2026-10-27 08:47 UTCEchelonGraph re-scored
  12. 2026-10-25 18:06 UTCEchelonGraph re-scored
  13. 2026-10-25 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  14. 2026-10-25 06:07 UTCEchelonGraph re-scored
  15. 2026-10-24 04:46 UTCEchelonGraph re-scored
  16. 2026-10-23 16:28 UTCEPSS rescoreEPSS 93% · 99th percentile
  17. 2026-10-23 03:22 UTCEchelonGraph re-scored
  18. 2026-10-22 02:01 UTCEchelonGraph re-scored
  19. 2026-10-21 00:39 UTCEchelonGraph re-scored
  20. 2026-10-20 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  21. 2026-10-19 23:16 UTCEchelonGraph re-scored
  22. 2026-10-18 21:55 UTCEchelonGraph re-scored
  23. 2026-10-18 08:33 UTCEchelonGraph re-scored
  24. 2026-10-17 20:34 UTCEchelonGraph re-scored
  25. 2026-10-16 19:13 UTCEchelonGraph re-scored
  26. 2026-10-15 17:51 UTCEchelonGraph re-scored
  27. 2026-10-14 16:30 UTCEchelonGraph re-scored
  28. 2026-10-14 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  29. 2026-10-14 08:49 UTCEchelonGraph re-scored
  30. 2026-10-12 18:52 UTCEchelonGraph re-scored
  31. 2026-10-11 21:41 UTCEchelonGraph re-scored
  32. 2026-10-11 17:29 UTCEchelonGraph re-scored
  33. 2026-10-11 13:15 UTCEchelonGraph re-scored
  34. 2026-10-06 19:24 UTCEchelonGraph re-scored
  35. 2026-10-06 15:14 UTCEPSS rescoreEPSS 93% · 99th percentile
  36. 2026-10-05 01:21 UTCEchelonGraph re-scored
  37. 2026-10-04 23:19 UTCEPSS rescoreEPSS 93% · 99th percentile
  38. 2026-09-28 22:03 UTCEchelonGraph re-scored
  39. 2026-09-27 21:51 UTCCISA KEV update
  40. 2026-09-26 19:41 UTCEchelonGraph re-scored
  41. 2026-09-25 19:35 UTCCISA KEV update
  42. 2026-09-25 14:55 UTCCISA KEV update
  43. 2026-09-24 19:31 UTCCISA KEV update
  44. 2026-09-24 17:11 UTCEchelonGraph re-scored
  45. 2026-09-24 14:00 UTCEPSS rescoreEPSS 93% · 99th percentile
  46. 2026-09-22 19:36 UTCCISA KEV update
  47. 2026-09-22 18:55 UTCEchelonGraph re-scored
  48. 2026-09-22 14:45 UTCEPSS rescoreEPSS 93% · 99th percentile
  49. 2026-09-21 21:53 UTCEchelonGraph re-scored
  50. 2026-09-21 19:09 UTCCISA KEV update
  51. 2026-09-20 20:41 UTCEchelonGraph re-scored
  52. 2026-09-20 20:13 UTCEPSS rescoreEPSS 93% · 99th percentile
  53. 2026-09-18 19:20 UTCCISA KEV update
  54. 2026-09-18 14:15 UTCCISA KEV update
  55. 2026-09-17 21:18 UTCEchelonGraph re-scored
  56. 2026-09-17 19:24 UTCEPSS rescoreEPSS 93% · 99th percentile
  57. 2026-09-16 14:10 UTCCISA KEV update
  58. 2026-09-14 19:24 UTCCISA KEV update
  59. 2026-09-11 18:49 UTCCISA KEV update
  60. 2026-09-11 13:38 UTCEchelonGraph re-scored
  61. 2026-09-11 09:33 UTCEPSS rescoreEPSS 93% · 99th percentile
  62. 2026-09-10 19:28 UTCCISA KEV update
  63. 2026-09-09 19:08 UTCCISA KEV update
  64. 2026-09-08 18:54 UTCCISA KEV update
  65. 2026-09-06 15:53 UTCEchelonGraph re-scored
  66. 2026-09-06 13:45 UTCEPSS rescoreEPSS 93% · 99th percentile
  67. 2026-09-05 18:50 UTCEchelonGraph re-scored
  68. 2026-09-05 15:25 UTCEPSS rescoreEPSS 93% · 99th percentile
  69. 2026-09-04 17:38 UTCCISA KEV update
  70. 2026-09-04 17:38 UTCEchelonGraph re-scored
  71. 2026-09-04 13:57 UTCEPSS rescoreEPSS 93% · 99th percentile
  72. 2026-09-02 17:33 UTCCISA KEV update
  73. 2026-08-31 14:19 UTCCISA KEV update
  74. 2026-08-30 19:29 UTCEchelonGraph re-scored

Publicly available exploits

(6 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 4 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/linux/http/apache_spark_rce_cve_2022_33891✓ verified
    Published Sep 7, 2022

    Apache Spark Unauthenticated Command Injection RCE

    Open source ↗
  • Nucleihttp/cves/2022/CVE-2022-33891.yaml
    Published Dec 23, 2022

    Apache Spark UI - Remote Command Injection

    Open source ↗
  • GitHub PoCAmoloHT/CVE-2022-33891
    Published Jul 30, 2022

    「💥」CVE-2022-33891 - Apache Spark Command Injection

    Open source ↗
  • GitHub PoCAkbarTrilaksana/cve-2022-33891
    Published Jul 20, 2022
    Open source ↗
  • GitHub PoCHuskyHacks/cve-2022-33891
    Published Jul 19, 2022

    Apache Spark Shell Command Injection Vulnerability

    Open source ↗
  • GitHub PoCW01fh4cker/cve-2022-33891
    Published Jul 18, 2022

    cve-2022-33891-poc

    Open source ↗

Frequently asked(6)

What is CVE-2022-33891?
CVE-2022-33891 is a critical-severity vulnerability; its CVE record was published on July 18, 2022. 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…
When was the CVE record for CVE-2022-33891 published?
The CVE record for CVE-2022-33891 was published on July 18, 2022. 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 October 23, 2025; the record at its source may have been updated since.
Is CVE-2022-33891 actively exploited?
Yes. CISA added CVE-2022-33891 to the Known Exploited Vulnerabilities catalog on March 7, 2023, affecting Apache Spark. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2022-33891?
CVE-2022-33891 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 (CRITICAL).
Which products are affected by CVE-2022-33891?
CVE-2022-33891 affects Apache Spark. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2022-33891?
A fix for CVE-2022-33891 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-33891 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-33891

Explore →

Is Your Infrastructure Affected by CVE-2022-33891?

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