PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-76279 Splunk CVE debrief

A vulnerability in Splunk Enterprise allows users with the run_collect capability to write events to internal indexes outside their configured index access. This is due to improper input validation of index names through the collect Search Processing Language (SPL) command. The issue affects Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15.

Vendor
Splunk
Product
Splunk Enterprise
CVSS
MEDIUM 4.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-07
Original CVE updated
2026-10-07
Advisory published
2026-10-07
Advisory updated
2026-10-07

Who should care

Splunk Enterprise administrators and users with the run_collect capability should assess their exposure and verify index access controls. They should also monitor collect command usage for potential security incidents and update Splunk Enterprise to prevent exploitation. Additionally, security teams and vulnerability management teams should review the vulnerability and its potential impact on their organization.

Why it matters

Defenders should prioritize verifying index access controls and monitoring collect command usage to prevent unauthorized data writes and potential security incidents.

  • Verify index access controls to prevent unauthorized data writes
  • Monitor collect command usage for potential security incidents
  • Update Splunk Enterprise to prevent exploitation

Technical summary

The vulnerability is caused by improper input validation of index names through the collect SPL command. This allows users with the run_collect capability to write events to internal indexes outside their configured index access. The issue affects Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerability can be mitigated by verifying index access controls and monitoring collect command usage. To prevent exploitation, defenders should prioritize updating Splunk Enterprise to a patched version.

Defensive priority

Defenders should prioritize verifying index access controls and monitoring collect command usage.

Recommended defensive actions

  • Verify index access controls for users with the run_collect capability
  • Monitor collect command usage for suspicious activity
  • Update Splunk Enterprise to version 10.4.3, 10.2.7, 10.0.10, or 9.4.15
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and potential impact. The vulnerability allows users with the run_collect capability to write events to internal indexes outside their configured index access due to improper input validation of index names through the collect SPL command. Affected versions include Splunk Enterprise below 10.4.3, 10.2.7, 10.0.10, and 9.4.15. Defenders should verify index access controls and monitor collect command usage.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-76279 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-76279

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-76279 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-76279

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.