Apache Spark History Server allows stored cross-site scripting through unescaped application names
There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later. This CVE is marked as "low" since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page. Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-32773US | — | — | ||
There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a mi… | ||||
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2026/09/01/4WEB
- https://github.com/apache/sparkPACKAGE
- https://github.com/apache/spark/commit/3c83c2c6a22fe384280b99bb753b14800b7e27e1WEB
- https://github.com/apache/spark/commit/e739b7d349dbd41b78d49bc8086cab63db057e14WEB
- https://github.com/apache/spark/pull/52851WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/pyspark/PYSEC-2026-3966.yamlWEB
- https://issues.apache.org/jira/browse/SPARK-53747WEB
- https://lists.apache.org/thread/k36prh3oxl1z6ov7w8rpmfnt07hmzw3vWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan