CVE-2025-60012: Apache Livy: Restrict file access

CVE-2025-60012 · Severity: low · CVSS 3.1 · Published 2026-03-13

Apache Livy: Restrict file access

Technologies: org.apache.livy:livy-server (Maven). Vendors: Maven.

Quick answers

Is CVE-2025-60012 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-60012 being exploited in the wild.
How severe is CVE-2025-60012?
Low severity, with a CVSS score of 3.1, published 13 March 2026.
Which products and versions are affected?
org.apache.livy:livy-server (Maven) ECOSYSTEM:introduced=0.7.0-incubating,fixed=0.9.0-incubating.
Is there a fix for CVE-2025-60012?
Yes. org.apache.livy:livy-server (Maven): upgrade to 0.9.0-incubating or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-60012?
Check whether you run org.apache.livy:livy-server (Maven) 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.livy:livy-server (Maven): upgrade to 0.9.0-incubating or later
    # set org.apache.livy:livy-server to 0.9.0-incubating in your pom.xml or build.gradle

Affected products

  • org.apache.livy:livy-server (Maven) ECOSYSTEM:introduced=0.7.0-incubating,fixed=0.9.0-incubating

Identifiers

  • CVE-2025-60012
  • GHSA-hm8x-rpgg-7855

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.