Improper Verification of Cryptographic Signature Affecting org.apache.spark:spark-network-common_2.12 package, versions [,3.4.4)[3.5.0,3.5.2)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHESPARK-13553868
- published15 Oct 2025
- disclosed15 Oct 2025
- creditUnknown
Introduced: 15 Oct 2025
NewCVE-2025-55039 (opens in a new tab)How to fix?
Upgrade org.apache.spark:spark-network-common_2.12 to version 3.4.4, 3.5.2 or higher.
Overview
org.apache.spark:spark-network-common_2.12 is an open-source distributed general-purpose cluster-computing framework.
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature when the spark.network.crypto.enabled is true and the cipher is not explicitly configured, resulting in the use of AES in CTR mode without authentication. An attacker can compromise the integrity of encrypted RPC traffic by performing man-in-the-middle attacks and modifying ciphertext undetected, potentially altering heartbeat messages or application data.
Workaround
This vulnerability can be mitigated by configuring the cipher to AES/GCM/NoPadding or enabling SSL encryption by setting spark.ssl.enabled to true.