Skip to content

Document new security vulnerability in Apache Spark#683

Open
miqowhy wants to merge 3 commits intoapache:asf-sitefrom
miqowhy:patch-1
Open

Document new security vulnerability in Apache Spark#683
miqowhy wants to merge 3 commits intoapache:asf-sitefrom
miqowhy:patch-1

Conversation

@miqowhy
Copy link
Copy Markdown

@miqowhy miqowhy commented Mar 24, 2026

Added details about CVE-2025-55039 vulnerability in Apache Spark, including severity, affected versions, descriptions, mitigations, and credit.

Two remarks:

  • I've taken the affected versions from @holdenk description, but I think all newer versions are also affected
  • For @holdenk 2nd mitigation - I think setting spark.ssl.enabled=true is not enough, you also need spark.ssl.rpc.enabled=true, at least that's what the documentation says

Added details about CVE-2025-55039 vulnerability in Apache Spark, including severity, affected versions, descriptions, mitigations, and credit.
@holdenk
Copy link
Copy Markdown
Contributor

holdenk commented Mar 24, 2026

Thanks for adding this! There's a build step you need to follow the for website changes to be visible.

@miqowhy
Copy link
Copy Markdown
Author

miqowhy commented Mar 24, 2026

Thanks for the reply, I'll follow the build step.

But in parallel I think we need to clarify the affected versions - I'll be reproducing the CVE to check, but is there any reason why newer versions are not affected by this vulnerability?

Looking at the docs of the latest version it looks like the vulnerable default is still in place.

Or am I missing something?

@holdenk
Copy link
Copy Markdown
Contributor

holdenk commented Mar 25, 2026

So I think https://issues.apache.org/jira/browse/SPARK-47172 indicates that the new config option is recommended for the new versions which if you follow the guidance in security settings is secure.

@miqowhy
Copy link
Copy Markdown
Author

miqowhy commented Mar 25, 2026

Thanks for adding this! There's a build step you need to follow the for website changes to be visible.

I've run the build step now, hope this is enough

@miqowhy
Copy link
Copy Markdown
Author

miqowhy commented Mar 27, 2026

Anything preventing us from merging? @holdenk @pan3793

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants