cve.bz

CVE-2025-55039 apache spark: Inadequate Encryption Strength

6.5 mediumEPSS 0.2%Fix available

Medium (6.5) in apache spark. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.spark:spark-network-common_2.13 3.4.4, 3.5.2.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-326 Inadequate Encryption Strength
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-55039 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-55039?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-55039?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-55039 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-55039

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-55039](https://cve.bz/cve/badge/CVE-2025-55039.svg)](https://cve.bz/cve/CVE-2025-55039)

HTML:

<a href="https://cve.bz/cve/CVE-2025-55039"><img src="https://cve.bz/cve/badge/CVE-2025-55039.svg" alt="CVE-2025-55039"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Sparkfrom 3.5.0 before 3.5.2
Apache Software Foundation Apache Sparkbefore 3.4.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6p6v-m64v-jx8qMavenorg.apache.spark:spark-network-common_2.13>=3.5.0 <3.5.23.5.2
GHSA-6p6v-m64v-jx8qMavenorg.apache.spark:spark-network-common_2.13<3.4.43.4.4
GHSA-6p6v-m64v-jx8qMavenorg.apache.spark:spark-network-common_2.12<3.4.43.4.4
GHSA-6p6v-m64v-jx8qMavenorg.apache.spark:spark-network-common_2.12>=3.5.0 <3.5.23.5.2
GHSA-6p6v-m64v-jx8qPyPIpyspark<3.4.43.4.4
GHSA-6p6v-m64v-jx8qPyPIpyspark>=3.5.0 <3.5.23.5.2
PYSEC-2025-184PyPIpyspark<3.4.4
>=3.5.0 <3.5.2
3.4.4, 3.5.2

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-192 Protocol Analysis Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON