← Back to results
Vulnerability record · public intelligence
CVE-2026-76344
HIGH

Path Traversal through the Search Dispatch REST API in Splunk Enterprise

Published Aug 19, 2026 · Updated Oct 23, 2026

Severity · CVSSHIGH · 7.7
Known exploitationNot listed
EPSS / likelihood0.41%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

Path Traversal through the Search Dispatch REST API in Splunk Enterprise

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
MEDIUM
Confidence
10%
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. advisory.splunk.com ↗

Record history

Published Aug 19, 2026 · Last refreshed Oct 23, 2026