What is CVE-2025-55039?

CVE-2025-55039 is a low-severity security vulnerability in org.apache.spark:spark-network-common_2.13 (maven), affecting versions >= 3.5.0, < 3.5.2. It is fixed in 3.5.2, 3.4.4.

Which packages are affected by CVE-2025-55039?

org.apache.spark:spark-network-common_2.13 (maven) versions >= 3.5.0, = 0, < 3.4.4.

Is there a fix for CVE-2025-55039?

Yes. CVE-2025-55039 is fixed in 3.5.2, 3.4.4. Upgrade to this version or later.

Is CVE-2025-55039 exploitable, and should I be worried?

Whether CVE-2025-55039 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-55039 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-55039 in org.apache.spark:spark-network-common_2.13 | Intelligent Application Security

Q: Which packages are affected by CVE-2025-55039?

org.apache.spark:spark-network-common_2.13 (maven) versions >= 3.5.0, = 0, < 3.4.4.

Q: Is there a fix for CVE-2025-55039?

Yes. CVE-2025-55039 is fixed in 3.5.2, 3.4.4. Upgrade to this version or later.

Q: Is CVE-2025-55039 exploitable, and should I be worried?

Whether CVE-2025-55039 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-55039 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-55039?

Upgrade: org.apache.spark:spark-network-common_2.13 to 3.5.2 or later, org.apache.spark:spark-network-common_2.13 to 3.4.4 or later, org.apache.spark:spark-network-common_2.12 to 3.4.4 or later, org.apache.spark:spark-network-common_2.12 to 3.5.2 or later, pyspark to 3.4.4 or later, pyspark to 3.5.2 or later.

Summary

This issue affects Apache Spark versions before 3.4.4, 3.5.2 and 4.0.0.

Apache Spark versions before 4.0.0, 3.5.2 and 3.4.4 use an insecure default network encryption cipher for RPC communication between nodes.

When spark.network.crypto.enabled is set to true (it is set to false by default), but spark.network.crypto.cipher is not explicitly configured, Spark defaults to AES in CTR mode (AES/CTR/NoPadding), which provides encryption without authentication.

This vulnerability allows a man-in-the-middle attacker to modify encrypted RPC traffic undetected by flipping bits in ciphertext, potentially compromising heartbeat messages or application data and affecting the integrity of Spark workflows.

To mitigate this issue, users should either configure spark.network.crypto.cipher to AES/GCM/NoPadding to enable authenticated encryption or enable SSL encryption by setting spark.ssl.enabled to true, which provides stronger transport security.

Impact

Affected versions

org.apache.spark:spark-network-common_2.13 (>= 3.5.0, < 3.5.2) org.apache.spark:spark-network-common_2.13 (< 3.4.4) org.apache.spark:spark-network-common_2.12 (< 3.4.4) org.apache.spark:spark-network-common_2.12 (>= 3.5.0, < 3.5.2) pyspark (>= 0, < 3.4.4) pyspark (>= 3.5.0, < 3.5.2)

Security releases

org.apache.spark:spark-network-common_2.13 → 3.5.2 (maven) org.apache.spark:spark-network-common_2.13 → 3.4.4 (maven) org.apache.spark:spark-network-common_2.12 → 3.4.4 (maven) org.apache.spark:spark-network-common_2.12 → 3.5.2 (maven) pyspark → 3.4.4 (pip) pyspark → 3.5.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.spark:spark-network-common_2.13 to 3.5.2 or later; org.apache.spark:spark-network-common_2.13 to 3.4.4 or later; org.apache.spark:spark-network-common_2.12 to 3.4.4 or later; org.apache.spark:spark-network-common_2.12 to 3.5.2 or later; pyspark to 3.4.4 or later; pyspark to 3.5.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-55039? CVE-2025-55039 is a low-severity security vulnerability in org.apache.spark:spark-network-common_2.13 (maven), affecting versions >= 3.5.0, < 3.5.2. It is fixed in 3.5.2, 3.4.4.
Which packages are affected by CVE-2025-55039?
- org.apache.spark:spark-network-common_2.13 (maven) (versions >= 3.5.0, < 3.5.2)
- org.apache.spark:spark-network-common_2.12 (maven) (versions < 3.4.4)
- pyspark (pip) (versions >= 0, < 3.4.4)
Is there a fix for CVE-2025-55039? Yes. CVE-2025-55039 is fixed in 3.5.2, 3.4.4. Upgrade to this version or later.
Is CVE-2025-55039 exploitable, and should I be worried? Whether CVE-2025-55039 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-55039 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-55039?
- Upgrade org.apache.spark:spark-network-common_2.13 to 3.5.2 or later
- Upgrade org.apache.spark:spark-network-common_2.13 to 3.4.4 or later
- Upgrade org.apache.spark:spark-network-common_2.12 to 3.4.4 or later
- Upgrade org.apache.spark:spark-network-common_2.12 to 3.5.2 or later
- Upgrade pyspark to 3.4.4 or later
- Upgrade pyspark to 3.5.2 or later