CVE-2026-76317: Splunk vulnerability (CVSS 8.8)

Description

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

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Splunk≥ 10.0.0 < 10.0.9 · ≥ 10.2.0 < 10.2.6 · ≥ 10.4.0 < 10.4.2 · ≥ 9.4.0 < 9.4.14

Remediation

Fixed in

Splunk≥ 10.0.9

Patch & vendor advisories

https://advisory.splunk.com/advisories/SVD-2026-0801

References

https://advisory.splunk.com/advisories/SVD-2026-0801Vendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-76317 being actively exploited?

CVE-2026-76317 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.56%.

How severe is CVE-2026-76317?

CVE-2026-76317 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.56% probability of exploitation.

Which products are affected by CVE-2026-76317?

Affected products include Splunk.

How do I fix CVE-2026-76317?

Upgrade affected software to a fixed version, for example Splunk 10.0.9 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-76317 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo