Skip to content
Medium 4.3

Improper Input Validation through HTTP Event Collector Token Names in Splunk Enterprise

CVE-2026-131193 First seen on SecPulse

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 resu...

Affected packages

PackageAffected → Fixed
SplunkSplunk Enterprise
≥ 10.4, < 10.4.5→ 10.4.5
≥ 10.2, < 10.2.9→ 10.2.9
≥ 10.0, < 10.0.12→ 10.0.12
≥ 9.4, < 9.4.17→ 9.4.17
Original description The description as published by the source.

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.

Source: CVE.org (CVE Program・cvelistV5) NVD

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details