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

CVE-2026-76330

Splunk Splunk Enterprise, splunk

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user could trick an authenticated user into opening a crafted link to Monitoring Console. When the authenticated user opens the link, Splunk Enterprise runs attacker-controlled Search Processing Language (SPL) using the permissions of that user. The injected SPL could access data and perform actions available to that user. The vulnerability is possible because Monitoring Console does not sufficiently validate data used to build forwarder dashboard searches. The vulnerability requires the attacker to p...

CVSS
7.1
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.1

Vulnerability overview

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user could trick an authenticated user into opening a crafted link to Monitoring Console. When the authenticated user opens the link, Splunk Enterprise runs attacker-controlled Search Processing Language (SPL) using the permissions of that user. The injected SPL could access data and perform actions available to that user. The vulnerability is possible because Monitoring Console does not sufficiently validate data used to build forwarder dashboard searches. The vulnerability requires the attacker to p...

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:H/PR:N/UI:R/S:U/C:H/I:H/A:L
CWE
CWE-20