No. Junglewise Threat Intelligence has no report of CVE-2025-54920 being exploited in the wild.
How severe is CVE-2025-54920?
Low severity, with a CVSS score of 3.1, published 16 March 2026.
Which products and versions are affected?
org.apache.spark:spark-core_2.10 (Maven) ECOSYSTEM:introduced=0,last_affected=2.2.3; org.apache.spark:spark-core_2.11 (Maven) ECOSYSTEM:introduced=0,last_affected=2.4.8; org.apache.spark:spark-core_2.12 (Maven) ECOSYSTEM:introduced=0,fixed=3.5.7; org.apache.spark:spark-core_2.13 (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.1; and 1 more.
Is there a fix for CVE-2025-54920?
Yes. org.apache.spark:spark-core_2.12 (Maven): upgrade to 3.5.7 or later; org.apache.spark:spark-core_2.13 (Maven): upgrade to 4.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-54920?
Check whether you run org.apache.spark:spark-core_2.10 (Maven), org.apache.spark:spark-core_2.11 (Maven), org.apache.spark:spark-core_2.12 (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
org.apache.spark:spark-core_2.12 (Maven): upgrade to 3.5.7 or later
# set org.apache.spark:spark-core_2.12 to 3.5.7 in your pom.xml or build.gradle
org.apache.spark:spark-core_2.13 (Maven): upgrade to 4.0.1 or later
# set org.apache.spark:spark-core_2.13 to 4.0.1 in your pom.xml or build.gradle