Is CVE-2026-76295 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-76295 being exploited in the wild.

How severe is CVE-2026-76295?

Medium severity, with a CVSS score of 4.3, published 21 October 2026.

Which products and versions are affected?

Splunk Secure Gateway below 3.10.12, 3.9.26, 3.8.7; Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11, 9.4.16.

Is there a fix for CVE-2026-76295?

Yes: fixed in Splunk Enterprise 10.4.4, 10.2.8, 10.0.11, 9.4.16; Splunk Secure Gateway 3.10.12, 3.9.26, 3.8.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-76295 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-76295?

Check whether you run Splunk Secure Gateway or Splunk Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-76295: Splunk Enterprise SPL injection in REST API through Secure Gateway

CVE-2026-76295 · Severity: medium · CVSS 4.3 · Published 2026-10-21

Splunk Enterprise and Secure Gateway are data analytics platforms used to index, search, and visualize machine data. A low-privilege user can inject malicious SPL (Splunk Processing Language) commands through unfiltered special characters in REST API requests, allowing them to view sensitive dashboards and reports beyond their authorized access level. This could lead to unauthorized disclosure of sensitive business intelligence and operational data.

Technologies: Splunk Secure Gateway, Splunk Enterprise. Vendors: Splunk.

Quick answers

Is CVE-2026-76295 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-76295 being exploited in the wild.
How severe is CVE-2026-76295?: Medium severity, with a CVSS score of 4.3, published 21 October 2026.
Which products and versions are affected?: Splunk Secure Gateway below 3.10.12, 3.9.26, 3.8.7; Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11, 9.4.16.
Is there a fix for CVE-2026-76295?: Yes: fixed in Splunk Enterprise 10.4.4, 10.2.8, 10.0.11, 9.4.16; Splunk Secure Gateway 3.10.12, 3.9.26, 3.8.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-76295 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-76295?: Check whether you run Splunk Secure Gateway or Splunk Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Splunk Enterprise 10.4.4, 10.2.8, 10.0.11, 9.4.16; Splunk Secure Gateway 3.10.12, 3.9.26, 3.8.7

Technical details

The vulnerability is a SPL injection flaw (CWE-943) in Splunk Secure Gateway's REST API handling. Unauthenticated or non-admin users can craft requests with special characters in filter values that bypass authorization checks on dashboard and report listings. The flaw exists because the gateway does not neutralize special characters before constructing SPL filter queries, allowing an attacker with any valid account to access objects they should not see.

Affected products

Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11, 9.4.16
Splunk Secure Gateway below 3.10.12, 3.9.26, 3.8.7

Timeline

2026-10-21: disclosed

References

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.