Skip to main content
VulnerabilityPublished

CVE-2026-131195: Splunk Enterprise · The software does not sufficiently track and release allocated memory after it has been used, which

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium · fixed in 10.4.5 : update Splunk Enterprise when convenient.

Data as of 19 Nov 2026, 20:07 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisco)CVSS 3.15.9
Patch
Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Splunk Enterprise to 10.4.5, 10.2.9, 10.0.12 or 9.4.17.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.4 <10.4.5
Fixed in
  • 10.4.5
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.9
Fixed in
  • 10.2.9
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.12
Fixed in
  • 10.0.12
SplunkSplunk EnterpriseAffected
  • >=9.4 <9.4.17
Fixed in
  • 9.4.17

AI-suggested

Upgrade affected Splunk Enterprise instances to versions 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later, where the issue is fixed. The vulnerability only affects instances with the [pubsubsvr-http] stanza enabled in server.conf, so disabling this stanza if not required can also mitigate the risk.

Description

CVE-2026-131195 is a denial of service vulnerability in Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17. It occurs when the HTTP PubSub broker, enabled via the [pubsubsvr-http] stanza in server.conf, fails to release memory after client disconnects. An unauthenticated attacker can exploit this by sending repeated HTTP PubSub channel subscription requests, causing memory exhaustion and service disruption.

References

Community reviews

Loading reviews…