CVE Intelligence
CISA KEV High Injection exploit reference

CVE-2022-33891 — Apache Spark Command Injection Vulnerability

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.

Published Jul 18, 2022 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: apache

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Mar 7, 2023 Detection templates (Nuclei) · 1Metasploit modules · 1Proofs of concept on GitHub · 10
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (nuclei, metasploit, github)+20
  • EPSS 93.2% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Mar 7, 2023
EPSS FIRST
93.24%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Apache Software Foundation
Apache Spark and 2 more
CVSS base
8.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Maven Org.apache.spark:spark-parent 2.12: fixed in version 3.2.2 — github.com (GitHub Security Advisories)
  • Pip Pyspark: fixed in version 3.1.3 — github.com (GitHub Security Advisories)
  • Pip Pyspark: fixed in version 3.2.2 — github.com (GitHub Security Advisories)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Mar 28, 2023 — passed 1297 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Apache Spark, Maven Org.apache.spark:spark-parent 2.12, Pip Pyspark).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Apache Spark ≥ 3.0.3 and earlier and ≤ 3.0.3≥ 3.1.1 to 3.1.2 and ≤ 3.1.2≥ 3.2.0 to 3.2.1 and ≤ 3.2.1 Vulnerable CVE Program (cve.org) e CISA ADP
Apache Software Foundation Apache Spark ≤ 3.0.3≥ 3.1.1 and ≤ 3.1.2≥ 3.2.0 and ≤ 3.2.1 Vulnerable NIST National Vulnerability Database
Maven Org.apache.spark:spark-parent 2.12 ≤ 3.0.3≥ 3.1.1 and < 3.2.2 Vulnerable GitHub Security Advisories
Pip Pyspark < 3.1.3≥ 3.2.0 and < 3.2.2 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.8 CVSS 3.1 High 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Mar 7, 2023
Federal deadline
Mar 28, 2023
passed 1297 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Detection templates (Nuclei)
Metasploit modules
Proofs of concept on GitHub

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 93.24%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before Mar 7, 2023 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · maven/org.apache.spark:spark-parent 2.12, pip/pyspark
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · apache/spark
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • Affected products added · apache software foundation/apache spark
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 8.8
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2023
  • Added to CISA KEV catalog
    Mar 6, 2023 · CISA
  • 2022
  • CVE published
    Jul 18, 2022 · apache

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

9 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
2023-03
what else CISA listed that month
Injection
same class
CWE-78
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-32773 There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows… Sep 2, 2026
  • CVE-2025-54920 Apache Spark: Spark History Server Code Execution Vulnerability Mar 16, 2026
  • CVE-2025-55039 Apache Spark, Apache Spark: RPC encryption defaults to unauthenticated AES-CTR mode, enabling man-in-the-middle ciphertext modification attacks Oct 15, 2025
  • CVE-2019-20445 HTTP Request Smuggling in Netty Jan 29, 2020

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-33891 is "Apache Spark Command Injection Vulnerability", rated High. It affects Apache Spark (Apache Software Foundation); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 93.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.