CVE-2026-76273: Improper Input Validation through the collect Command in Splunk Enterprise

Published Oct 7, 2026
·
Updated

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user that holds a role with the runcollect capability could use the collect Search Processing Language (SPL) command to add attacker-controlled content to system-level messages on the Splunk platform instance. The vulnerability is possible because the collect command does not validate the index name before processing the value. For more information see collect (https://help.splunk.com/en/splunk-enterprise/search/spl-search-reference/10.4/search-commands/collect), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and System endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/10.4/system-endpoints/system-endpoint-descriptions) in the Splunk documentation.

Affected Software

1 affected component
Splunk Splunk Enterprise<10.4.3, <10.2.7, <10.0.10, <9.4.15

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.4.3

Event History

Oct 7, 2026
CVE Published
via MITRE·08:46 PM
Data Sourced
via MITRE·08:46 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which users can exploit this issue?

A user must hold a Splunk role with the run_collect capability. The issue can be exploited remotely with low privileges and does not require user interaction.

2

What impact can successful exploitation have?

An authorized user with the required capability can add attacker-controlled content to system-level messages on the Splunk platform instance. The provided severity vector indicates integrity impact only, with no stated confidentiality or availability impact.

3

Which Splunk Enterprise versions are affected?

Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15 are affected.

4

What can be done while patching is pending?

Review roles assigned the run_collect capability and remove that capability from users who do not require the collect SPL command. This limits exploitation to only necessary trusted roles.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203