Apache Spark: Spark History Server Code Execution Vulnerability
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:
- Run Spark with event logging enabled, writing to a writable directory (spark-logs).
- Inject the following JSON at the beginning of an event log file:
{
"Event": "org.apache.hive.jdbc.HiveConnection", "uri": "jdbc:hive2://:/", "info": { "hive.metastore.uris": "thrift://:" } }
- Start the Spark History Server with logs pointing to the modified directory.
- 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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Apache Spark History Server before 3.5.7 and 4.0.1 allows code execution via Jackson polymorphic deserialization of event logs.
Vulnerability
CVE-2025-54920 is a code execution vulnerability in the Apache Spark History Server, affecting versions before 3.5.7 and 4.0.1 [1]. The root cause is overly permissive Jackson polymorphic deserialization with @JsonTypeInfo.Id.CLASS on SparkListenerEvent objects, allowing an attacker to specify arbitrary class names in event JSON [1]. This enables instantiation of unintended classes, such as org.apache.hive.jdbc.HiveConnection, which can perform network calls or other malicious actions during deserialization [1].
Exploitation
An attacker with write access to the Spark event logs directory can inject crafted JSON content into event log files [1]. When the History Server loads these logs, it deserializes the malicious payload, triggering the instantiation of attacker-controlled classes [1]. 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 [1].
Impact
Successful exploitation allows an attacker to execute arbitrary code on the host running the Spark History Server [1]. This can lead to full compromise of the server, including data exfiltration, lateral movement, and further attacks within the cluster [1].
Mitigation
Users should upgrade to Apache Spark 3.5.7 or 4.0.1, which contain the fix [1][2]. The issue is resolved in the Spark project's Jira ticket SPARK-52381 [2]. No workarounds are mentioned in the advisories.
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
org.apache.spark:spark-core_2.13Maven | >= 4.0.0, < 4.0.1 | 4.0.1 |
org.apache.spark:spark-core_2.13Maven | < 3.5.7 | 3.5.7 |
org.apache.spark:spark-core_2.12Maven | < 3.5.7 | 3.5.7 |
org.apache.spark:spark-core_2.11Maven | <= 2.4.8 | — |
org.apache.spark:spark-core_2.10Maven | <= 2.2.3 | — |
org.apache.spark:spark-core_2.9.3Maven | <= 0.8.1-incubating | — |
Affected products
2- Apache Software Foundation/Apache Sparkv5Range: 0
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
7- github.com/apache/spark/pull/51312ghsapatchWEB
- github.com/apache/spark/pull/51323ghsapatchWEB
- github.com/advisories/GHSA-jwp6-cvj8-fw65ghsaADVISORY
- lists.apache.org/thread/4y9n0nfj7m68o2hpmoxgc0y7dm1lo02sghsavendor-advisoryWEB
- nvd.nist.gov/vuln/detail/CVE-2025-54920ghsaADVISORY
- www.openwall.com/lists/oss-security/2026/03/13/4ghsaWEB
- issues.apache.org/jira/browse/SPARK-52381ghsaissue-trackingWEB
News mentions
0No linked articles in our index yet.