Apache Livy: Unauthorized directory access

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2025-66249: 0.61% estimated exploitation activity in the next 30 days; percentile 49.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

13 Mar 2026, 21:31 UTC

Last modified by the source

16 Mar 2026, 18:45 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h84f-4ff9-8hc3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-66249

Advisory: Apache Livy: Unauthorized directory access
IDs: CVE-2025-66249, GHSA-h84f-4ff9-8hc3
Record: https://patchnext.com/advisories/cve-2025-66249 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.livy:livy-server 0.9.0-incubating. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.livy:livy-server: affected >= 0.3.0-incubating, < 0.9.0-incubating; fixed in 0.9.0-incubating

## Suggested inspection (read-only)
- Maven org.apache.livy:livy-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.livy:livy-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h84f-4ff9-8hc3 (GitHub-reviewed advisory GHSA-h84f-4ff9-8hc3 lists affected ranges: Maven org.apache.livy:livy-server >=0.3.0-incubating <0.9.0-incubating)

Commands are suggestions: review each one before running it.