Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2026-76268 Scanner

CVE-2026-76268 Scanner - Remote Code Execution (RCE) vulnerability in Splunk Enterprise

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
9
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
9.8
CVSScritical
Exploitable remotely over the internet · no authentication required.
Description

In Splunk Enterprise versions below 10.4.3 and 10.2.7, an unauthenticated user with network access to the Patroni Representational State Transfer (REST) Application Programming Interface (API) on a search head cluster member could execute attacker-controlled operating-system commands. The vulnerability is possible because this interface does not require authentication for critical configuration operations. For more information see Sidecar configuration settings (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.2/splunk-sidecars/sidecar-configuration-settings) in the Splunk documentation. Splunk Enterprise versions 10.0.x and 9.4.x are not affected.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
Splunk Enterpriseby Splunk
AFFECTED< 10.4.3→SAFE ✓≥ 10.4.3
Updated Nov 6, 2026View on NVD →
Detail

Splunk Enterprise is a software platform used for searching, monitoring, and analyzing machine-generated big data, via a web-style interface. Organizations use this platform to turn data into valuable business insights by indexing, correlating, and visualizing real-time data. System administrators and IT professionals often rely on Splunk Enterprise to monitor system performance and security metrics across large networks. The software can handle huge volumes of data while offering the flexibility to query data through various methods. Financial institutions, telecommunication companies, and government agencies are among its prominent users. Its highly configurable nature allows integration with numerous tools and services, enhancing its utility in diverse environments.

The vulnerability found in Splunk Enterprise is a Remote Code Execution (RCE) issue. This vulnerability arises when the Patroni REST API, used as a PostgreSQL sidecar, is exposed without authentication on certain versions. An attacker could exploit this weakness to perform actions they would normally not have permission to execute, such as injecting arbitrary commands. This issue is particularly critical because it enables an unauthenticated user to achieve code execution with the privileges of PostgreSQL. The exploitation requires network access to the Patroni port, significantly increasing the risk if not properly secured. User awareness and system patches are crucial to mitigating this vulnerability.

To exploit this vulnerability, an attacker would need to access the Patroni port and use it to send malicious commands via the REST API. This process involves PATCHing the /config endpoint to set a harmful archive_command. Following this, the attacker can make a POST request to the /restart endpoint to trigger the malicious command, leading to remote code execution under PostgreSQL privileges. The vulnerability affects specific versions of Splunk Enterprise, necessitating careful review and updating of affected systems.

If exploited, this RCE vulnerability could have severe consequences, including unauthorized access to sensitive data and system operations. The attacker could gain control over the Splunk Enterprise server, potentially leading to data manipulation, data theft, or further exploits within the organization's network. Such a breach could damage the organization's reputation, lead to financial losses, and expose it to legal liabilities due to compromised data protection measures. Immediate action to mitigate this vulnerability is highly advisable.

REFERENCES

Solution Advice
  • Upgrade Splunk Enterprise to version 10.2.7 or 10.4.3 or later to fix the vulnerability.
  • Restrict network access to the Patroni port to trusted networks only.
  • Apply patches and updates provided by the vendor promptly to prevent exploitation.
  • Implement network segmentation and firewall rules to control access to vulnerable endpoints.
  • Monitor for unknown or unauthorized access attempts to the Patroni REST API.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.