Cyber Resilience

CVE-2026-76344

Splunk 9.4.0 – 9.4.14

Published
19 August 2026
Modified
26 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
EPSS Score 0.0030 22th percentile
Risk Priority 54 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

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

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 22th 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 write dispatch metadata to an arbitrary location on the host by supplying a crafted search identifier to…

more

a Representational State Transfer (REST) API endpoint and affect system integrity on the host. The vulnerability is possible because Splunk Enterprise does not validate the search identifier before using it to create a dispatch directory. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

CWE(s)
CWE-27

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-76254Same product: Splunk Splunk
CVE-2026-76317Same product: Splunk Splunk
CVE-2026-76354Same product: Splunk Splunk
CVE-2026-76331Same product: Splunk Splunk
CVE-2026-76316Same product: Splunk Splunk
CVE-2023-22942Same product: Splunk Splunk
CVE-2026-20253Same product: Splunk Splunk
CVE-2026-76355Same product: Splunk Splunk
CVE-2024-36984Same product: Splunk Splunk
CVE-2026-76325Same 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 directly stops untrusted pathnames containing ../ sequences from being used to construct traversals outside 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 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.

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.28 Secure coding mostly match
prevents

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

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

Security testing in development catches path-traversal flaws before release but does not itself implement the control.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and path sanitization that directly prevents directory traversal.

A.8.26 Application security requirements partial match
prevents

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

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

Secure architecture principles discourage unsafe path construction but do not prescribe the specific coding fix.

A.8.3 Information access restriction partial match
mitigates

Information access restriction can limit which files are reachable, reducing impact but not preventing the traversal vector.

References