CVE-2025-66249
CVE-2025-66249 is a medium-severity vulnerability in Apache Livy with a CVSS 3.x base score of 6.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.
Key facts
- Severity: Medium (CVSS 3.x base score 6.3)
- EPSS exploit prediction: 1% (53rd percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-208639
- Weakness: CWE-22
- Affected product: Apache Livy
- Published:
- Last modified:
Description
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Livy. This issue affects Apache Livy: from 0.3.0 before 0.9.0. The vulnerability can only be exploited with non-default Apache Livy Server settings. If the configuration value "livy.file.local-dir-whitelist" is set to a non-default value, the directory checking can be bypassed. Users are recommended to upgrade to version 0.9.0, which fixes the issue.
Frequently asked questions
- What is CVE-2025-66249?
- Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Livy. This issue affects Apache Livy: from 0.3.0 before 0.9.0. The vulnerability can only be exploited with non-default Apache Livy Server settings. If the configuration value "livy.file.local-dir-whitelist" is set to a non-default value, the directory checking can be bypassed. Users are recommended to upgrade to version 0.9.0, which fixes the issue.
- How severe is CVE-2025-66249?
- CVE-2025-66249 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
- Is CVE-2025-66249 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-66249?
- CVE-2025-66249 affects Apache Livy. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2025-66249?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2025-66249 have an EU (EUVD) identifier?
- Yes. CVE-2025-66249 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-208639.
- When was CVE-2025-66249 published?
- CVE-2025-66249 was published on 2026-03-13 and last updated on 2026-06-17.
References
- https://lists.apache.org/thread/1xwphsfn4jbtym4k4o0zlvwfogwqwwc3
- http://www.openwall.com/lists/oss-security/2026/03/12/2
Affected products (1)
- cpe:2.3:a:apache:livy:*:*:*:*:*:*:*:*
More vulnerabilities in Apache Livy
- CVE-2025-60012 — Medium (CVSS 6.3): Malicious configuration can lead to unauthorized file access in Apache Livy. This issue affects Apache Livy 0.7.0 and…
- CVE-2021-26544 — Medium (CVSS 5.4): Livy server version 0.7.0-incubating (only) is vulnerable to a cross site scripting issue in the session name. A…
All CVEs affecting Apache Livy →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-77312 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429…
- CVE-2026-121351 — Critical (CVSS 10.0): Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')…
- CVE-2026-121489 — Critical (CVSS 10.0): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau. The…
- CVE-2026-122013 — Critical (CVSS 10.0): A vulnerability was detected in Comfast CF-WR632AX 2.6.0.1. Affected by this vulnerability is an unknown functionality…
- CVE-2026-61738 — Critical (CVSS 10.0): SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to…
- CVE-2026-112690 — Critical (CVSS 10.0): This issue was addressed with improved input validation. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2…