Skip to content
VulniPulse
Advisory severityHigh8.8Splunk

High [CVE-2026-76316] Stored SPL Injection through Deployment Server Broker Registration in Splunk Enterprise

This high-severity Splunk advisory covers CVE-2026-76316 affecting Splunk Enterprise.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-76316 Source published Source updated

VulniPulse record published

Affected products & platforms
SplunkSplunk Enterprise
Open source advisory

Android app · Google Play

Monitor future Splunk CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.9, and 9.4.14, an unauthenticated user who can reach the Splunk management port could store a Search Processing Language (SPL) pipeline that runs when an administrator opens the Add Data forwarder workflow.

The SPL pipeline could access all relevant data, affect system integrity, and affect availability of the Splunk platform instance. The SPL injection is possible because Deployment Server client identifiers are placed into dispatched searches without neutralizing special characters.

Successful exploitation requires an administrator to open the affected Add Data forwarder workflow after the unauthenticated user registers a crafted Deployment Server client identity. For more information see Forward data ( ) and About agent management ( ) in the Splunk documentation.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.1
  • Splunk Enterprise 10.2 before 10.2.5
  • Splunk Enterprise 10.0 before 10.0.9
  • Splunk Enterprise 9.4 before 9.4.14

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 10.4.1
  • 10.2.5
  • 10.0.9
  • 9.4.14

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • For more information see Forward data (https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.2/how-to-get-data-into-your-splunk-deployment/forward-data) and About agent management (https://help.splunk.com/en/splunk-enterprise/administer/update-your-deployment/10.4/agent-management/about-agent-management) in the Splunk documentation.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.