Cyber Resilience

CVE-2026-76317

Splunk 9.4.0 – 9.4.14

Published
19 August 2026
Modified
21 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.8
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:H
EPSS Score 0.0038 31th percentile
Risk Priority 63 floored blend · peak EPSS

Summary

CVE-2026-76317 is a high-severity Path Traversal: '/dir/../filename' (CWE-26) vulnerability in Splunk Splunk. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 31th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could move files that the user account running Splunk Enterprise can read into a lookup that the user…

more

controls. The user could then access all relevant data and affect system integrity and availability on the search head. The vulnerability is possible because the lookup configuration endpoint does not resolve lookup source paths before checking whether they stay inside the allowed lookup staging area. For more information see About lookups (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/use-lookups-in-splunk-web/about-lookups) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

CWE(s)
CWE-26

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.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-76344Same product: Splunk Splunk
CVE-2026-76354Same product: Splunk Splunk
CVE-2026-76331Same product: Splunk Splunk
CVE-2023-22942Same product: Splunk Splunk
CVE-2026-76316Same product: Splunk Splunk
CVE-2026-76254Same product: Splunk Splunk
CVE-2026-76355Same product: Splunk Splunk
CVE-2026-20253Same product: Splunk Splunk
CVE-2024-36984Same product: Splunk Splunk
CVE-2026-76336Same product: Splunk Splunk

Affected Assets

splunk
splunk
9.4.0 — 9.4.14 · 10.0.0 — 10.0.9 · 10.2.0 — 10.2.6

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation partial match

Input validation structurally stops untrusted path sequences from being used to construct filenames that escape the intended directory.

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 this weakness.

ID.RA-01 partial match
prevents

Vulnerability identification processes will discover path traversal flaws during scanning or testing.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce directory restrictions that reduce exploitability.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

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

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and path canonicalization that directly prevent directory traversal sequences.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against path traversal and other injection flaws.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific coding fix.

A.8.28 Secure coding partial match
prevents

Secure coding standards require neutralizing '../' sequences and canonicalizing paths before file operations.

References