SECUFOCUSNOW
Home›CVE index›CVE-2026-76344
ReviewHigh

CVE-2026-76344

Splunk Splunk Enterprise, splunk

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

CVSS
7.7
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.08.20
PRIORITY ASSESSMENT

Review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.7

Vulnerability overview

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

Affected product and versions

Product
Splunk Splunk Enterprise, splunk
Affected versions
>= 10.4 < 10.4.2, >= 10.2 < 10.2.6, >= 10.0 < 10.0.9, >= 9.4 < 9.4.14, >= 9.4.0 < 9.4.14, >= 10.0.0 < 10.0.9, >= 10.2.0 < 10.2.6, >= 10.4.0 < 10.4.2
Fixed versions
9.4.14, 10.0.9, 10.2.6, 10.4.2

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Splunk Splunk Enterprise, splunk and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
CWE
CWE-27