CVE-2026-131193: Improper Input Validation through HTTP Event Collector Token Names in Splunk Enterprise
This Splunk advisory covers CVE-2026-131193 in Splunk Enterprise.
- CVE-2026-131193
Key facts
- Vendor rating
- Medium, CVSS 4.3
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N· base score 4.3, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: low. Availability impact: none.- Weakness
- CWE-20 The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Splunk Enterprise 10.4 before 10.4.5; Splunk Enterprise 10.2 before 10.2.9; Splunk Enterprise 10.0 before 10.0.12 and 1 more below
- Fixed in
- 10.4.5, 10.2.9, 10.0.12 and 1 more below
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
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 ( ) and Set up and use HTTP Event Collector in Splunk Web ( ) in the Splunk documentation.
Text from the source record.
- Splunk Enterprise 10.4 before 10.4.5
- Splunk Enterprise 10.2 before 10.2.9
- Splunk Enterprise 10.0 before 10.0.12
- Splunk Enterprise 9.4 before 9.4.17
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-131193
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- As a result, the token remains active and can continue ingesting events even after administrative attempts to revoke it.
Support dates for the fixed release lines
- Splunk Enterprise 10.4: support ends
- Splunk Enterprise 10.2: support ends
- Splunk Enterprise 10.0: support ends
- Splunk Enterprise 9.4: support ends
More Splunk advisories
CVE-2026-131197Nov 19, 2026Privilege Escalation through Splunk Web Dashboards in Splunk App for Splunk ObservabilityCVE-2026-131196Nov 19, 2026Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk EnterpriseCVE-2026-131195Nov 19, 2026Denial of Service (DoS) through HTTP PubSub Channel Subscriptions in Splunk EnterpriseCVE-2026-131194Nov 19, 2026Stored Cross-Site Scripting (XSS) through Splunk Web Views in Splunk EnterpriseCVE-2026-131192Nov 19, 2026Authentication Bypass through the REST API in Splunk EnterpriseCVE-2026-131191Nov 19, 2026Sensitive Information Disclosure through the Deployment Server REST API in Splunk
Get an email when Splunk Enterprise publishes the next one.
See Splunk Enterprise's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.