Quick answers
- Is CVE-2026-32773 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32773 being exploited in the wild.
- How severe is CVE-2026-32773?
- Medium severity, with a CVSS score of 6.1, published 2 September 2026.
- Which products and versions are affected?
- Apache Spark before 3.5.8; org.apache.spark:spark-core_2.12 (Maven) >= 3.0.0, < 3.5.8, ECOSYSTEM:introduced=3.0.0,fixed=3.5.8; org.apache.spark:spark-core_2.13 (Maven) >= 3.0.0, < 3.5.8, ECOSYSTEM:introduced=3.0.0,fixed=3.5.8; pyspark (PyPI) >= 3.0.0, < 3.5.8, ECOSYSTEM:introduced=3.0.0,fixed=3.5.8.
- Is there a fix for CVE-2026-32773?
- Yes. org.apache.spark:spark-core_2.12 (Maven): upgrade to 3.5.8 or later; org.apache.spark:spark-core_2.13 (Maven): upgrade to 3.5.8 or later; pyspark (PyPI): upgrade to 3.5.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32773 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-32773?
- Check whether you run Apache Spark, org.apache.spark:spark-core_2.12 (Maven), org.apache.spark:spark-core_2.13 (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.apache.spark:spark-core_2.12 (Maven): upgrade to 3.5.8 or later
# set org.apache.spark:spark-core_2.12 to 3.5.8 in your pom.xml or build.gradle - org.apache.spark:spark-core_2.13 (Maven): upgrade to 3.5.8 or later
# set org.apache.spark:spark-core_2.13 to 3.5.8 in your pom.xml or build.gradle - pyspark (PyPI): upgrade to 3.5.8 or later
pip install "pyspark>=3.5.8"
Technical details
The Spark History Server fails to properly escape user-supplied input (likely from Spark job names or configuration) when rendering it in the web frontend, allowing Cross-Site Scripting (XSS) injection. An attacker with permissions to submit Spark jobs can craft a malicious job name containing JavaScript code that executes in the browser of any administrator or high-privilege user who views the Spark History Server web interface. This requires the attacker to have job-submission privileges and a victim with higher permissions to visit the affected page. The vulnerability is fixed in Spark 3.5.8 and later versions.
Affected products
- Apache Spark before 3.5.8
Identifiers
- CVE-2026-32773
- BIT-SPARK-2026-32773
- GHSA-9437-39hj-3c93
- PYSEC-2026-3966
Timeline
- 2026-09-02: disclosed