CVE-2026-131193 json
Improper Input Validation through HTTP Event Collector Token Names in Splunk Enterprise
published 6h ago modified 5h ago also EUVD-2026-130588
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Splunk Splunk Enterprise 9.4.17, 10.0.12, 10.2.9, 10.4.5
Is CVE-2026-131193 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- Splunk Splunk Enterprise
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
Sources
- CVE List CVE-2026-131193
- NVD CVE-2026-131193
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.