Security Vulnerabilities in Splunk Enterprise - October 2026

CVE-2026-76287: Authorization Bypass in the Data Management REST API in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4, a user that holds a role with the preview_data_management_pipeline capability or edit_data_management_pipeline_job capability could read or delete Data Management SPL2 preview jobs and results outside their ownership scope. The vulnerability is possible because the Data Management Representational State Transfer (REST) API verifies the required capability but does not verify that the requested preview job belongs to the requester. The affected Data Management REST API is available only when the Edge Processor feature is turned on. The Edge Processor feature is turned off by default. For more information see Set up a data management control plane and Getting sample data for previewing data transformations in the Splunk documentation.

Bug ID: VULN-106927

CWE: CWE-639

CVSSv3.1 Score: 5.4, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Mitigations and Workarounds

Turn off the SPL2 preview sidecar by setting spl2_preview_enabled to false in the server.conf configuration file if you do not use SPL2 previews for Edge Processor pipelines. Restart Splunk Enterprise for the change to take effect. For more information see the server.conf configuration specification file in the Splunk documentation.

Acknowledgments: oxship

CVE-2026-76288: Denial of Service (DoS) through Splunk Web Content-Type Header Parsing in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could send a single crafted request to the Splunk Web JavaScript logger endpoint and cause Splunk Web to stop responding to requests. Splunk Web remains unavailable until Splunk Enterprise is restarted. The vulnerability is possible because Splunk Web does not limit request-header parsing before processing the request.

Bug ID: VULN-101483

CWE: CWE-400

CVSSv3.1 Score: 7.5, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigations and Workarounds

The vulnerability affects instances with Splunk Web turned on. Turning Splunk Web off is a possible workaround. See Disable unnecessary Splunk Enterprise components and the web.conf configuration specification file for more information on turning off Splunk Web.

Acknowledgments: Pedro Cardoso (tvmpt)

CVE-2026-76289: Denial of Service (DoS) through the REST API in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who does not hold the “admin” or “power” Splunk roles could make the Splunk Enterprise instance unavailable to other users by sending a request to the Representational State Transfer (REST) API endpoint for lookup table files. The affected instance requires a restart to restore service. The vulnerability is possible because the endpoint does not limit resource use when it processes response field selections. For more information see Endpoints reference list and About configuring role-based user access in the Splunk documentation.

Bug ID: VULN-102565

CWE: CWE-770

CVSSv3.1 Score: 6.5, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Mitigations and Workarounds

None

Acknowledgments: Pedro Cardoso (tvmpt)

CVE-2026-76290: Denial of Service (DoS) through Unauthenticated Package Downloads over the REST API in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4, 10.2.8, and 10.0.11, an unauthenticated user could send repeated requests to the Edge Processor package download endpoint in the Splunk Pipeline Builders app. The requests could cause the Splunk daemon to consume excessive system resources and potentially stop responding. The vulnerability is possible because the endpoint accepts package download requests without authentication and reads and base64-encodes the complete package in memory for each request. After upgrading, prepare all existing Edge Processor instances, turn on authentication for Edge Processor package downloads, and restart Splunk Enterprise. For more information, see Enable authentication for Edge Processor package downloads.

Bug ID: VULN-99234

CWE: CWE-400

CVSSv3.1 Score: 7.5, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigations and Workarounds

Turn off or remove the Splunk Pipeline Builders app. This action makes the Edge Processor solution unavailable. For more information see Manage app and add-on objects in the Splunk documentation.

Acknowledgments: Pedro Cardoso (tvmpt)

CVE-2026-76291: Improper Access Control through Scheduled Search Safeguards in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the schedule_search capability could bypass the expected safeguards in the scheduled search workflow. The user could then run risky Search Processing Language (SPL) commands that disclose or alter Splunk Enterprise data or disrupt Splunk Enterprise availability. The vulnerability is possible because the Splunk Enterprise search scheduler does not apply SPL safeguards for risky commands to scheduled searches. For more information see SPL safeguards for risky commands in the Splunk documentation. For more information see authorize.conf in the Splunk documentation.

Bug ID: VULN-91851

CWE: CWE-284

CVSSv3.1 Score: 8.8, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Mitigations and Workarounds

None

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76292: Missing Authorization through REST API Endpoints in Splunk Secure Gateway

Description

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, a low-privileged user that does not hold the “admin” Splunk role or the “sc_admin” Splunk Secure Gateway role could read mobile alert notification data for other users through Splunk Secure Gateway App Key Value Store (KV Store) Representational State Transfer (REST) API endpoints. The vulnerability is possible because the affected Splunk Secure Gateway App Key Value Store collections do not enforce user-level authorization for read requests. For more information see About the app key value store and About configuring role-based user access in the Splunk documentation.

Additional Solution

Upgrade Splunk Secure Gateway to versions 3.10.12, 3.9.26, and 3.8.73 or higher.

Bug ID: VULN-77576

CWE: CWE-862

CVSSv3.1 Score: 6.5, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Mitigations and Workarounds

Turn off or remove the Splunk Secure Gateway app. See Manage app and add-on objects in the Splunk documentation. Note: Splunk Mobile, Spacebridge, and Mission Control rely on functionality in the Splunk Secure Gateway app. If you do not use any of these apps, features, or functionality, as a potential mitigation, you may turn off or remove the app.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76293: Remote Code Execution (RCE) through Splunk Web Manager Extensible Markup Language (XML) in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.3, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_manager_xml capability could execute arbitrary operating-system commands using the permissions of the user account running Splunk Enterprise by opening the affected configuration in the Splunk Web Manager page. The vulnerability is possible because Splunk Web evaluates user-controlled expressions from Manager XML without sufficiently restricting the expression syntax.

Bug ID: VULN-95473

CWE: CWE-94

CVSSv3.1 Score: 7.2, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Mitigations and Workarounds

None

Acknowledgments: Jasper Westerman

CVE-2026-76294: Improper Access Control in Field Extraction Management in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who does not hold the “admin” or “power” Splunk roles could move field extractions or field transformations to apps for which the user does not have read access. The vulnerability is possible because the Representational State Transfer (REST) API does not validate destination app access before it processes field extraction and field transformation move operations. For more information see Use the Field extractions page and Manage knowledge object permissions in the Splunk documentation.

Bug ID: VULN-44876

CWE: CWE-862

CVSSv3.1 Score: 4.3, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Mitigations and Workarounds

None

Acknowledgments: Azeem Tak (dedsec_hacker)

CVE-2026-76295: SPL Injection through the REST API in Splunk Secure Gateway

Description

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, a user who does not hold the “admin” or “power” Splunk roles could view dashboard and report listings beyond the requested filter scope while remaining within objects that the user can access. The vulnerability is possible because Splunk Secure Gateway does not neutralize special characters in values before it creates filters for dashboard and report requests. For more information see About configuring role-based user access in the Splunk documentation.

Additional Solution

Upgrade Splunk Secure Gateway to versions 3.10.12, 3.9.26, and 3.8.73 or higher.

Bug ID: VULN-73644

CWE: CWE-943

CVSSv3.1 Score: 4.3, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Mitigations and Workarounds

Turn off or remove the Splunk Secure Gateway app. See Manage app and add-on objects in the Splunk documentation. Note: Splunk Mobile, Spacebridge, and Mission Control rely on functionality in the Splunk Secure Gateway app. If you do not use any of these apps, features, or functionality, as a potential mitigation, you may turn off or remove the app.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76296: Missing Authorization through Sourcetype Renaming in Splunk Web for Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who does not hold the “admin” or “power” Splunk roles could create, move, edit, or delete sourcetype renaming configurations that they own in apps that they do not have permission to access. The vulnerability is possible when Splunk Web is turned on because Splunk Web does not verify the required app permissions before it performs sourcetype renaming operations. For more information see Rename source types at search time in the Splunk documentation.

Bug ID: VULN-56679

CWE: CWE-862

CVSSv3.1 Score: 4.3, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Mitigations and Workarounds

None

Acknowledgments: Saidina Hikam (xzyhellsing), M Mahdan Argya Syarif (0xbeludan)

CVE-2026-76297: Federated Search Provider State Change through Cross-Site Request Forgery (CSRF) in Splunk Web for Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could trick a user that holds a role with the edit_federated_providers capability into turning off all federated search providers. Successful exploitation could temporarily prevent federated searches from retrieving data from remote datasets. The vulnerability is possible because the federated provider Representational State Transfer (REST) API accepts GET requests for actions that change provider state. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Run federated searches over remote Splunk platform deployments and Define roles on the Splunk platform with capabilities in the Splunk documentation.

Bug ID: VULN-24586

CWE: CWE-352

CVSSv3.1 Score: 4.2, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L

Mitigations and Workarounds

None

Acknowledgments: Anton (therceman)

CVE-2026-76298: Use of Hard-coded Cryptographic Key in the PostgreSQL Sidecar Service in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.4 and 10.2.8, a user who does not hold the “admin” or “power” Splunk roles could derive the PostgreSQL sidecar database superuser password and run arbitrary operating system commands as the user account running Splunk Enterprise on search head cluster members. The vulnerability is possible because the PostgreSQL sidecar service derives a privileged database password from the search head cluster identifier that appears in search job logs. For more information see About configuring role-based user access, server.conf, and Sidecar configuration settings in the Splunk documentation.

Bug ID: VULN-80238

CWE: CWE-321

CVSSv3.1 Score: 8.8, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Mitigations and Workarounds

If you cannot immediately upgrade to a fixed version, turn off the PostgreSQL sidecar service. Add the following stanza in the server.conf configuration file: [postgres] disabled = true. Restart Splunk Enterprise for the change to take effect. Do not apply this workaround if you use Edge Processor, OpAmp, or SPL2 data pipelines on the instance. Turning off PostgreSQL breaks these features and can cascade to dependent sidecar processes. Core search, indexing, and dashboard functionality are not affected. For more information see Sidecar configuration settings in the Splunk documentation.

Acknowledgments: Ofir Alkoby, Security Researcher, a.security