Splunk Enterprise up to 10.4.1 Management Port Listener privileges management

Summaryinfo

A vulnerability has been found in Splunk Enterprise up to 9.3.13/9.4.12/10.0.8/10.2.5/10.4.1 and classified as very critical. This issue affects some unknown processing of the component Management Port Listener. This manipulation causes privileges management. The identification of this vulnerability is CVE-2026-76259. The attack can only be executed locally. There is no exploit available.

Detailsinfo

A vulnerability has been found in Splunk Enterprise up to 9.3.13/9.4.12/10.0.8/10.2.5/10.4.1 and classified as very critical. Affected by this vulnerability is an unknown part of the component Management Port Listener. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

In Splunk Enterprise for Windows versions below 10.4.2, 10.2.6, 10.0.9, 9.4.13, and 9.3.14, a local user with access to the Windows host could bind to the management port before Splunk Enterprise starts, intercept authentication tokens from child processes, and use those tokens to compromise all relevant data and system integrity available to the user account running Splunk Enterprise. The vulnerability is possible because the Windows management-port listener does not apply exclusive address binding protections before the service starts.

The advisory is shared at advisory.splunk.com. This vulnerability is known as CVE-2026-76259 since 08/19/2026. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/20/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 9.3.14, 9.4.13, 10.0.9, 10.2.6 or 10.4.2 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Log Management Software

Vendor

• Splunk

Name

• Enterprise

Version

• 9.3.0
• 9.3.1
• 9.3.2
• 9.3.3
• 9.3.4
• 9.3.5
• 9.3.6
• 9.3.7
• 9.3.8
• 9.3.9
• 9.3.10
• 9.3.11
• 9.3.12
• 9.3.13
• 9.4.0
• 9.4.1
• 9.4.2
• 9.4.3
• 9.4.4
• 9.4.5
• 9.4.6
• 9.4.7
• 9.4.8
• 9.4.9
• 9.4.10
• 9.4.11
• 9.4.12
• 10.0.0
• 10.0.1
• 10.0.2
• 10.0.3
• 10.0.4
• 10.0.5
• 10.0.6
• 10.0.7
• 10.0.8
• 10.2.0
• 10.2.1
• 10.2.2
• 10.2.3
• 10.2.4
• 10.2.5
• 10.4.0
• 10.4.1

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion