RPC traffic modification via unauthenticated AES-CTR
Published Oct 15, 2025 · Updated Oct 15, 2025
Cryptographic integrity failure in Apache Spark before 3.4.4 and 3.5.0 through 3.5.1 allows man-in-the-middle attackers to alter RPC traffic. When network crypto is enabled without an explicit cipher, AuthEngine selects AES/CTR/NoPadding, whose malleable ciphertext is not authenticated before RPC messages are processed. The issue is reachable only by an on-path attacker when spark.network.crypto.enabled is true while the cipher remains unset; altered heartbeats or application data can corrupt workflow integrity.
Summary
What happened
Cryptographic integrity failure in Apache Spark before 3.4.4 and 3.5.0 through 3.5.1 allows man-in-the-middle attackers to alter RPC traffic. When network crypto is enabled without an explicit cipher, AuthEngine selects AES/CTR/NoPadding, whose malleable ciphertext is not authenticated before RPC messages are processed. The issue is reachable only by an on-path attacker when spark.network.crypto.enabled is true while the cipher remains unset; altered heartbeats or application data can corrupt workflow integrity.
The record
- CVE
- CVE-2025-55039
- Published
- Oct 15, 2025
- Updated
- Oct 15, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Spark
- Classifications
- CWE-326, CWE-347, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.4.4
- Affected versionversion=3.5.0 <3.5.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo