dbcve.org
KyuubiApplication · Apache

CVE-2025-66518

HIGH · 8.8 CVSS v3.1 Published 2026-01-05
Fix available
A fix is available. Upgrade to 1.10.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Any client who can access to Apache Kyuubi Server via Kyuubi frontend protocols can bypass server-side config kyuubi.session.local.dir.allow.list and use local files which are not listed in the config. This issue affects Apache Kyuubi: from 1.6.0 through 1.10.2. Users are recommended to upgrade to version 1.10.3 or upper, 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 Kyuubi Server contains an authorization bypass vulnerability where clients accessing the server via frontend protocols can circumvent the kyuubi.session.local.dir.allow.list configuration, enabling access to local filesystem files that should be restricted.

MitigationUpgrade Apache Kyuubi to version 1.10.3 or later to obtain the fix for this allow list bypass vulnerability.

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
KyuubiApplication
Affected:>= 1.6.0, < 1.10.3

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
High
Integrity
High
Availability
High

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

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 installed Apache Kyuubi version
    Check the Kyuubi server version by reviewing the release documentation, startup logs, or running 'kyuubi --version' if the command is available. Common locations include the 'RELEASE' file in the installation directory or the build metadata.
    Affected if The installed version is 1.6.0 through 1.10.2 (inclusive)
  2. Locate the kyuubi.session.local.dir.allow.list configuration
    Search Kyuubi configuration files (typically in conf/ directory) for the setting 'kyuubi.session.local.dir.allow.list' in properties files such as kyuubi-defaults.conf, kyuubi-site.xml, or application.conf depending on deployment.
    Affected if This configuration option is defined and specifies allowed local directories for session access
  3. Verify frontend protocol access is enabled
    Check if Kyuubi is configured to accept connections via frontend protocols (such as HTTP, REST, or thrift-based interfaces). Review the 'kyuubi.frontend.bind.host' and 'kyuubi.frontend.bind.port' settings in the configuration files.
    Affected if Frontend network listeners are active and accessible to clients
  4. Confirm local directory access feature is in use
    Determine whether any sessions or jobs are utilizing local directory access functionality that would reference the allow.list configuration. Review session logs or query history for file operations that might use this setting.
    Affected if The local directory allow.list is actively being used to control filesystem access

You are affected if your Kyuubi version is between 1.6.0 and 1.10.2 inclusive AND you have the kyuubi.session.local.dir.allow.list configuration in use, as clients connecting via frontend protocols could bypass this restriction to access restricted local filesystem paths.

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 1.10.3 or later
Fixed in 1.10.3
Interim mitigation

Upgrade Apache Kyuubi to version 1.10.3 or later to obtain the fix for this allow list bypass vulnerability.

Recommended fix High confidence

1.10.3 or later

  1. Backup your current Kyuubi configuration and any custom settings
  2. Download Apache Kyuubi version 1.10.3 or later from the official Apache distribution mirrors (https://kyuubi.apache.org/releases.html)
  3. Stop the running Kyuubi Server instance
  4. Install or extract the new version to your deployment directory
  5. Restore your configuration (or verify that existing configs are compatible with 1.10.3)
  6. Start the Kyuubi Server
  7. Verify the server starts successfully and the kyuubi.session.local.dir.allow.list config is enforced as expected

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

Fix this in Kyuubi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66518 — 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-66518 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