Apache Livy: Unauthorized directory access
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A path traversal vulnerability in Apache Livy (0.3.0 before 0.9.0) allows bypassing directory whitelist checks when a non-default configuration is used.
Vulnerability
Overview
CVE-2025-66249 is a path traversal vulnerability (Improper Limitation of a Pathname to a Restricted Directory) in Apache Livy, affecting versions from 0.3.0 up to but not including 0.9.0. The root cause lies in the way Livy server's handling of the livy.file.local-dir-whitelist configuration property. When this setting is changed from its default value, the directory validation logic can be bypassed, allowing users to specify paths outside the intended whitelist [1][3].
Exploitation
Conditions
The vulnerability is exploitable only when the Apache Livy Server is configured with a non-default value for livy.file.local-dir-whitelist. This is a server-side configuration setting that restricts which local directories Livy can access for file operations. An attacker would need to be able to submit requests to the Livy REST API, but no additional authentication is required beyond that for normal API usage. The exploit does not require pre-authentication if the server is exposed without authentication, which is a known deployment scenario [1][3].
Impact
An attacker who successfully bypasses the directory whitelist can read, write, or delete files in arbitrary locations on the Livy server's filesystem, outside the intended restricted directories. This could lead to disclosure of sensitive data (e.g., configuration files, credentials), modification of critical system files, or denial of service. The impact is limited to the file system permissions of the Livy server process [1][3].
Mitigation
The vendor recommends upgrading to Apache Livy version 0.9.0, which fixes the issue. Users who cannot immediately upgrade should ensure that the livy.file.local-dir-whitelist configuration is set to its default value (empty value. No workaround is provided for installations that require non-default whitelist settings prior to upgrading [1][3].
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
org.apache.livy:livy-serverMaven | >= 0.3.0-incubating, < 0.9.0-incubating | 0.9.0-incubating |
Affected products
2- Apache Software Foundation/Apache Livyv5Range: 0.3.0-incubating
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4- github.com/advisories/GHSA-h84f-4ff9-8hc3ghsaADVISORY
- lists.apache.org/thread/1xwphsfn4jbtym4k4o0zlvwfogwqwwc3ghsavendor-advisoryWEB
- nvd.nist.gov/vuln/detail/CVE-2025-66249ghsaADVISORY
- www.openwall.com/lists/oss-security/2026/03/12/2ghsaWEB
News mentions
0No linked articles in our index yet.