CVE-2026-76331 SPL Injection through the REST API in Splunk Enterprise

High 8.1 Published Updated

Attackers can inject Search Processing Language via the REST API to access unauthorized data and compromise system integrity in Splunk Enterprise.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-76331?

CVE-2026-76331 is a high-severity code injection vulnerability in Splunk Splunk, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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 inject Search Processing Language (SPL) into saved-search dispatch requests. This could allow for unauthorized access to all relevant data and affect system integrity within Splunk Enterprise. The vulnerability is possible because Splunk Enterprise does not correctly validate caller-supplied time values before using them in saved-search dispatch. For more information see Search endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/10.2/search-endpoints/search-endpoint-descriptions) in the Splunk documentation.

Weakness: CWE-943

Which versions are affected by CVE-2026-76331?

It affects 1 product.

Products include Splunk Splunk.

How do I fix CVE-2026-76331?

No fix has been published for CVE-2026-76331 yet. Limit exposure of the affected software until one is available.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2026-76331 being exploited?

There is no known exploitation of CVE-2026-76331 in the wild and no public exploit code.

All Splunk Splunk vulnerabilities

Sources

Also known as GHSA-f473-74xq-6v94.

Is CVE-2026-76331 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free