Skip to content
VulniPulse
Medium6.0Splunk

Medium [CVE-2026-76345] Remote Code Execution (RCE) through the REST API in Splunk Enterprise

This medium-severity Splunk advisory covers CVE-2026-76345 affecting Splunk Enterprise.

CVE-2026-76345 Published Aug 19, 2026Updated by vendor Aug 19, 2026
Affected products & platforms
SplunkSplunk Enterprise
Open vendor 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 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

In Splunk Enterprise versions below 10.4.2, a user with a high-privilege Splunk role that can manage search head clustering could use the search head cluster member bundle Representational State Transfer (REST) API to write files to locations that the user account running Splunk Enterprise can write to, which could allow for remote code execution.

Successful exploitation could result in access to all relevant data and could affect the integrity and availability of the Splunk deployment. The vulnerability does not affect Splunk Enterprise versions below 10.4.

The vulnerability is possible because the search head cluster member bundle REST API does not enforce the expected authorization boundary and does not validate bundle paths before accepting bundle content.

For more information see Using the REST API reference ( ), About configuring role-based user access ( ), and About distributed search ( ) in the Splunk documentation.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.2

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions
  • 10.4.2

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation

Upgrade to a fixed release: 10.4.2. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 1 hour 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.