Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.9
Spark data-processing framework may run code with wrong privileges
published 10 days ago
Summary
Versions of Apache Spark before 3.4 let a job submitted with spark-submit choose a different user name, but an attacker can add harmful classes to the job’s classpath and make the code run with the submitting user’s rights. This can expose any system that relies on the proxy‑user feature, such as services that launch Spark jobs on behalf of others. Upgrade Spark to version 3.4 or later and keep the setting that blocks custom classpaths in cluster mode.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Alpine:3.24 | docker hardened images | janusgraph-1.0 | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | janusgraph-1.1 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | janusgraph-1.0 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | janusgraph-1.1 | All versions |
Original advisory text
In Apache Spark versions prior to 3.4.0, applications using spark-submit can specify a 'proxy-user' to run as, limiting…
In Apache Spark versions prior to 3.4.0, applications using spark-submit can specify a 'proxy-user' to run as, limiting privileges. The application can execute code with the privileges of the submitting user, however, by providing malicious configuration-related classes on the classpath. This affects architectures relying on proxy-user, for example those using Apache Livy to manage submitted applications.
Update to Apache Spark 3.4.0 or later, and ensure that
spark.submit.proxyUser.allowCustomClasspathInClusterMode is set to its
default of "false", and is not overridden by submitted applications.
Update to Apache Spark 3.4.0 or later, and ensure that
spark.submit.proxyUser.allowCustomClasspathInClusterMode is set to its
default of "false", and is not overridden by submitted applications.
References
- https://scout.docker.com/v/DHI-p5mo-7e2b-4kx7-542l Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2023-22946 Vendor Advisory
- https://github.com/advisories/GHSA-329j-jfvr-rhr6 Vendor Advisory
- https://github.com/degant/spark/commit/bfba57724d2520e0fcaa7990f7257c21d11cd75a Patch
- https://github.com/apache/spark/pull/41428 Patch
- https://github.com/apache/spark/pull/39474 Patch
- https://github.com/apache/spark/commit/909da96e1471886a01a9e1def93630c4fd40e74a Patch
- https://lists.apache.org/thread/yllfl25xh5tbotjmg93zrq4bzwhqc0gv Vendor Advisory
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker full control (estimated)
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
DHI-p5mo-7e2b-4kx7-542l · OSV
Track software like this
Free during beta