Skip to content
Threat Brief

← All advisories

CVE-2026-131195

Medium 5.9No known exploitationFix available

Denial of Service (DoS) through HTTP PubSub Channel Subscriptions in Splunk Enterprise

Record last updated

CVSS score

5.9

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 22% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-401

Patching and mitigation

Patch status
Fix available (source: CVE record (cisco))
Fix documented (source date)
Vendor solution
Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.
Mitigation
Turn off the HTTP PubSub broker by setting `disabled` = `true` in the `server.conf` configuration file if you do not use agent management over HTTP. For more information see [server.conf configuration specification file](https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.4/configuration-file-reference/10.4.4-configuration-file-reference/server.conf) in the Splunk documentation.
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
SplunkSplunk Enterprisefrom 10.0 before 10.0.1210.0.12CVE Program
SplunkSplunk Enterprisefrom 10.2 before 10.2.910.2.9CVE Program
SplunkSplunk Enterprisefrom 10.4 before 10.4.510.4.5CVE Program
SplunkSplunk Enterprisefrom 9.4 before 9.4.179.4.17CVE Program

Timeline

  1. Disclosure

    CVE record published by cisco

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (cisco)

    Source: CVE record (cisco) (opens in a new tab)

Vendor guidance and references