dbcve.org
KyuubiApplication · Apache

CVE-2026-52680

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-30
Fix available
A fix is available. Upgrade to 1.12.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 3 weeks old

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
Apache Kyuubi REST batch multipart upload handling uses the client-supplied multipart filename when creating a temporary uploaded resource. A remote attacker who can access the REST batch upload endpoint can provide path traversal sequences in the filename and cause the Kyuubi server process to write controlled content outside the intended upload directory, subject to filesystem permissions. This issue affects Apache Kyuubi: from 1.7.0 through 1.11.1. Users are recommended to upgrade to version 1.12.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 Kyuubi's REST batch multipart upload feature directly uses the client-provided filename when creating temporary upload resources without sanitization, allowing path traversal sequences (e.g., ../../) to write files outside the intended upload directory. A remote attacker with access to the upload endpoint can overwrite arbitrary filesystem locations subject to permissions.

MitigationUpgrade Apache Kyuubi to version 1.12.0 or later, which contains the fix for proper filename sanitization in multipart uploads.

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.7.0, < 1.12.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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
    Run 'kyuubi --version' or check the kyuubi-core jar manifest, or look in the installed packages/ directory for the version
    Affected if The installed version is 1.7.0 or higher but lower than 1.12.0
  2. Locate Kyuubi configuration files
    Find kyuubi-defaults.conf or kyuubi-site.xml in the Kyuubi conf directory (typically $KYUUBI_HOME/conf)
    Affected if Configuration files exist and Kyuubi is deployed
  3. Check for REST batch upload endpoint exposure
    Inspect configuration for 'kyuubi.frontend.rest.batch.upload' or similar REST/-upload related settings in the config files
    Affected if Batch upload functionality is enabled in the configuration
  4. Review upload directory configuration
    Look for 'kyuubi.upload.dir' or similar upload directory settings in the configuration to identify the intended upload location
    Affected if An upload directory is configured (indicating the feature is in use)
  5. Check for anomalous file creation logs
    Search Kyuubi audit or application logs for path traversal patterns (../) in upload filename fields or unexpected file creation events outside the designated upload directory
    Affected if Logs show files created with path traversal sequences or files appearing outside the intended upload directory

You are affected if your installed Kyuubi version falls within 1.7.0 to 1.11.x inclusive and the REST batch multipart upload feature is enabled or has been used.

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.12.0 or later
Fixed in 1.12.0
Interim mitigation

Upgrade Apache Kyuubi to version 1.12.0 or later, which contains the fix for proper filename sanitization in multipart uploads.

Recommended fix High confidence

1.12.0

  1. Download Apache Kyuubi version 1.12.0 from the official Apache releases repository (https://kyuubi.apache.org/release.html)
  2. Stop the currently running Kyuubi server instance
  3. Replace the existing Kyuubi installation with version 1.12.0
  4. Review the release notes for version 1.12.0 to ensure compatibility with your existing configurations and dependencies
  5. Restart the Kyuubi server with the new version
  6. Verify that the REST batch multipart upload functionality works correctly and that the path traversal vulnerability is mitigated
Caveat Review 1.12.0 release notes for any configuration or API changes that may affect existing workloads

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

Fix this in Kyuubi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
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,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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