Cyber Resilience

CVE-2026-62391

Path Traversal in Apache Kyuubi 1.6.0 – 1.12.0

Published
31 July 2026
Modified
10 August 2026
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0052 42th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2026-62391 is a high-severity Path Traversal (CWE-22) vulnerability in Apache Kyuubi. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The security fix for CVE-2025-66518 is incomplete. Any client who can access to Apache Kyuubi Server via Kyuubi frontend protocols can bypass server-side config kyuubi.session.local.dir.allowlist via unprefixed Spark config aliases. This issue affects Apache Kyuubi: from 1.6.0 before 1.12.0. Users…

more

are recommended to upgrade to version 1.12.0, which fixes the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-66518Same product: Apache Kyuubi
CVE-2023-34478Same vendor: Apache
CVE-2025-66249Same vendor: Apache
CVE-2026-23907Same vendor: Apache
CVE-2023-22887Same vendor: Apache
CVE-2026-49818Same vendor: Apache
CVE-2026-33227Same vendor: Apache
CVE-2023-49735Same vendor: Apache
CVE-2026-33929Same vendor: Apache
CVE-2026-29220Same vendor: Apache

Affected Assets

apache
kyuubi
1.6.0 — 1.12.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes special path elements before pathname construction occurs.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent directory traversal flaws.

ID.RA-01 partial match
prevents

Vulnerability identification processes will discover path traversal weaknesses during code or configuration review.

PR.AA-05 partial match
prevents

Least-privilege file permissions and access enforcement can limit the damage from a successful traversal.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards require neutralizing '../' sequences and using safe file APIs, eliminating this exact weakness.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

mitigates

Information access restriction limits which files an application may read or write.

References