CVE-2026-131193
Improper Input Validation through HTTP Event Collector Token Names in Splunk Enterprise
Description
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user holding a role with the edit_token_http capability could create a persistent HTTP Event Collector (HEC) token that cannot be disabled or deleted via the Representational State Transfer (REST) API or Splunk Web. As a result, the token remains active and can continue ingesting events even after administrative attempts to revoke it. The vulnerability is possible because HTTP Event Collector token creation accepts names that later management operations cannot process. For more information see authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.5-configuration-file-reference/authorize.conf) and Set up and use HTTP Event Collector in Splunk Web (https://help.splunk.com/en/splunk-enterprise/get-data-in/get-started-with-getting-data-in/10.6/get-data-with-http-event-collector/set-up-and-use-http-event-collector-in-splunk-web) in the Splunk documentation.
INFO
Published Date :
Nov. 19, 2026, 7:55 p.m.
Last Modified :
Nov. 19, 2026, 7:55 p.m.
Remotely Exploit :
No
Source :
cisco
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | d1c1063e-7a18-46af-9102-31f8928bc633 | ||||
| CVSS 3.1 | MEDIUM | MITRE-CVE |
Solution
- Update Splunk Enterprise to a fixed version.
- Verify HEC tokens can be disabled or deleted.
- Restrict edit_token_http capability.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-131193 vulnerability anywhere in the article.