CVE-2026-76295 Splunk CVE debrief

Who should care

Defenders responsible for Splunk Enterprise and Splunk Secure Gateway deployments should assess exposure and verify versions to prevent potential unauthorized access to dashboard and report listings.

Why it matters

Defenders should prioritize verifying and updating Splunk Enterprise and Splunk Secure Gateway versions to prevent potential unauthorized access to dashboard and report listings. This vulnerability allows users without 'admin' or 'power' roles to view listings beyond their requested filter scope.

• Potential unauthorized access to dashboard and report listings.
• Possible elevation of privileges for users without 'admin' or 'power' roles.
• Need for verification and updates to Splunk Enterprise and Splunk Secure Gateway versions.

Technical summary

The vulnerability exists in Splunk Secure Gateway due to improper neutralization of special characters in values before creating filters for dashboard and report requests. This allows users without 'admin' or 'power' roles to view dashboard and report listings beyond their requested filter scope. The vulnerability is confirmed in Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and Splunk Secure Gateway versions below 3.10.12, 3.9.26, and 3.8.73. Defenders should prioritize verifying and updating Splunk Enterprise and Splunk Secure Gateway versions to prevent potential unauthorized access to dashboard and report listings.

Defensive priority

Defenders should prioritize verifying and updating Splunk Enterprise and Splunk Secure Gateway versions to prevent potential unauthorized access to dashboard and report listings.

Recommended defensive actions

• Verify and update Splunk Enterprise and Splunk Secure Gateway to the latest versions.
• Restrict access to dashboard and report listings based on user roles.
• Monitor for suspicious activity related to unauthorized access to dashboard and report listings.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability is confirmed in Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and Splunk Secure Gateway versions below 3.10.12, 3.9.26, and 3.8.73. Users without 'admin' or 'power' roles may be able to view unauthorized dashboard and report listings.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.