How severe is GHSA-6p6v-m64v-jx8q?

No CVSS score has been assigned to GHSA-6p6v-m64v-jx8q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6p6v-m64v-jx8q?

GHSA-6p6v-m64v-jx8q affects the following packages: org.apache.spark:spark-network-common_2.13 (Maven), org.apache.spark:spark-network-common_2.13 (Maven), org.apache.spark:spark-network-common_2.12 (Maven), org.apache.spark:spark-network-common_2.12 (Maven), pyspark (PyPI), pyspark (PyPI). Ecosystems affected: Maven, PyPI.

How do I fix GHSA-6p6v-m64v-jx8q?

Update org.apache.spark:spark-network-common_2.13 to 3.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6p6v-m64v-jx8q is resolved across your whole dependency graph.

How do I detect GHSA-6p6v-m64v-jx8q in my Maven, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.spark:spark-network-common_2.13, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6p6v-m64v-jx8q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6p6v-m64v-jx8q?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6p6v-m64v-jx8q can be triaged on real exposure rather than presence alone.

Is GHSA-6p6v-m64v-jx8q actively exploited in the wild?

No public exploit code has been indexed for GHSA-6p6v-m64v-jx8q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6p6v-m64v-jx8q?

GHSA-6p6v-m64v-jx8q has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6p6v-m64v-jx8q?

GHSA-6p6v-m64v-jx8q is classified as CWE-326 (CWE-326), CWE-347 (CWE-347). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6p6v-m64v-jx8q published, and has it been updated?

GHSA-6p6v-m64v-jx8q was published on October 15, 2025 and was last updated on June 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven🐍 PyPI

Not in CISA KEV

GHSA-6p6v-m64v-jx8q — spark-network-common_2.13

Fix: apache/spark@05ba74e

GHSA-6p6v-m64v-jx8q is a CWE-326 vulnerability in org.apache.spark:spark-network-common_2.13. A fix is available for org.apache.spark:spark-network-common_2.13 — see the affected versions and patch details below.

Apache Spark has Inadequate Encryption Strength

Also known asCVE-2025-55039PYSEC-2025-184

Published

Oct 15, 2025

Updated

Jun 8, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6p6v-m64v-jx8q.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

6 pkgs affected

☕org.apache.spark:spark-network-common_2.13☕org.apache.spark:spark-network-common_2.13☕org.apache.spark:spark-network-common_2.12☕org.apache.spark:spark-network-common_2.12🐍pyspark🐍pyspark

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.spark:spark-network-common_2.13`	≥ 3.5.0&&< 3.5.2	3.5.2`org.apache.spark:spark-network-common_2.13:3.5.2`
☕Maven	`org.apache.spark:spark-network-common_2.13`	all versions	3.4.4`org.apache.spark:spark-network-common_2.13:3.4.4`
☕Maven	`org.apache.spark:spark-network-common_2.12`	all versions	3.4.4`org.apache.spark:spark-network-common_2.12:3.4.4`
☕Maven	`org.apache.spark:spark-network-common_2.12`	≥ 3.5.0&&< 3.5.2	3.5.2`org.apache.spark:spark-network-common_2.12:3.5.2`
🐍PyPI	`pyspark`	all versions	3.4.4`pip install --upgrade 'pyspark==3.4.4'`
🐍PyPI	`pyspark`	≥ 3.5.0&&< 3.5.2	3.5.2`pip install --upgrade 'pyspark==3.5.2'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.spark:spark-network-common_2.13, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.spark:spark-network-common_2.13 to 3.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6p6v-m64v-jx8q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6p6v-m64v-jx8q can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6p6v-m64v-jx8q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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, potent

O3 Security · Impact-Aware SCA

Is GHSA-6p6v-m64v-jx8q in your dependencies?

O3 Security finds GHSA-6p6v-m64v-jx8q across Maven, PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works