dbcve.org
LivyApplication · Apache

CVE-2025-66249

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 0.9.0 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Livy contains a path traversal vulnerability in the file upload functionality. When the 'livy.file.local-dir-whitelist' configuration is set to a non-default value, the directory restriction checking can be bypassed, allowing attackers to access files outside the intended whitelist directory.

MitigationUpgrade to Apache Livy version 0.9.0 or later. Alternatively, ensure 'livy.file.local-dir-whitelist' is not configured with non-default values if upgrading is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LivyApplication
Affected:>= 0.3.0, < 0.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Livy installation and version
    Check for Livy installation directory and locate the version file or check the Livy server version via its API endpoint (e.g., /batches or /sessions), or inspect build files like pom.xml if source is available
    Affected if The installed version is >= 0.3.0 and < 0.9.0
  2. Locate Livy configuration file
    Find the livy.conf file, typically located in $LIVY_HOME/conf/ or /etc/livy/
    Affected if Configuration file exists and is accessible
  3. Check livy.file.local-dir-whitelist setting
    Inspect livy.conf for the 'livy.file.local-dir-whitelist' property and note its configured value
    Affected if The property is set to a value other than the default (i.e., a custom directory path is specified)
  4. Verify file upload endpoint accessibility
    Review whether the Livy REST API file upload endpoints (/files/upload or similar) are exposed and accessible in the environment
    Affected if File upload functionality is enabled and reachable without additional network restrictions

A user is affected if Apache Livy version is 0.3.0 through 0.8.x AND the livy.file.local-dir-whitelist is configured to a non-default custom directory path, allowing potential path traversal attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.9.0 or later
Fixed in 0.9.0
Interim mitigation

Upgrade to Apache Livy version 0.9.0 or later. Alternatively, ensure 'livy.file.local-dir-whitelist' is not configured with non-default values if upgrading is not immediately feasible.

Recommended fix High confidence

0.9.0

  1. Plan and schedule the Livy upgrade during a maintenance window
  2. Back up the current Livy configuration files (livy.conf, spark-defaults.conf, and any custom configurations)
  3. Review current configuration settings, especially the 'livy.file.local-dir-whitelist' setting
  4. Download Apache Livy version 0.9.0 from the official Apache Livy repository (https://livy.apache.org/)
  5. Install Livy 0.9.0 in a staging or test environment first
  6. Migrate the backed-up configuration to the new version, preserving any necessary custom settings
  7. Verify that 'livy.file.local-dir-whitelist' is appropriately configured (preferably remove non-default values if not strictly needed)
  8. Test Livy functionality in the test environment to ensure the upgrade works correctly
Caveat Review release notes for any breaking changes between your current version and 0.9.0 before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Livy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66249 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66249 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data