CVE-2026-131195: Denial of Service (DoS) through HTTP PubSub Channel Subscriptions in Splunk Enterprise

Published Nov 19, 2026
·
Updated

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could send repeated HTTP PubSub channel subscription requests that cause a Denial of Service (DoS) by permanently increasing memory usage until Splunk Enterprise exhausts available memory. The vulnerability affects instances that turn on the [pubsubsvr-http] stanza in server.conf because the HTTP PubSub broker does not release memory associated with a channel after the client disconnects.

Affected Software

1 affected component
Splunk Splunk Enterprise<10.4.5, <10.2.9, <10.0.12, <9.4.17

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.6.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.4.5
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.2.9
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.12
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.4.17

Event History

Nov 19, 2026
CVE Published
via MITRE·07:55 PM
Data Sourced
via MITRE·07:55 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Affected deployments are Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 that have the [pubsubsvr-http] stanza enabled in server.conf.

2

Does an attacker need credentials or user interaction?

No. An unauthenticated attacker can repeatedly submit HTTP PubSub channel subscription requests; no user interaction is required.

3

What happens during exploitation?

Memory associated with a PubSub channel is not released after the client disconnects. Repeated requests can permanently increase memory consumption until the Splunk Enterprise instance exhausts available memory, causing denial of service.

4

What mitigation is available if an upgrade cannot be performed immediately?

Disable the [pubsubsvr-http] stanza in server.conf to remove the affected HTTP PubSub broker exposure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203