CVE-2026-76279: Improper Input Validation of Index Names 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 write events to internal indexes outside the index access configured for the role. The vulnerability is possible because Splunk Enterprise does not normalize whitespace in an index name before applying configured index-access restrictions for the role. 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 How indexing works (https://help.splunk.com/en/splunk-enterprise/administer/manage-indexers-and-indexer-clusters/10.4/indexing-overview/how-indexing-works) 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
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.7
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.10
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.4.15

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 could abuse this issue?

An authenticated Splunk Enterprise user assigned a role with the run_collect capability could exploit it. Users without that capability are not identified as able to use this path.

2

What is the security impact?

The user could write events to internal indexes that are outside the index access configured for their role. The stated impact is unauthorized modification of indexed event data, not disclosure or service disruption.

3

How can an administrator determine whether remediation is needed?

Review Splunk Enterprise versions and identify roles that grant run_collect. Versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15 are affected when users with that capability are present.

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