LearnCTEM.com, Best CTEM Learning Platform
CVE Intelligence Hub

CVE-2026-131182: Splunk Enterprise Security Vulnerability

CVE-2026-131182 explained: high Security Vulnerability in Splunk Enterprise. CVSS 7.6. Affected versions, detection, fixes and CTEM priority.

Last updated: Nov 19, 2026

CVSS
7.6 HIGH
EPSS
n/a
CISA KEV
Not listed
CWE
CWE-116

Sources: National Vulnerability Database, CVE.org, CISA KEV, FIRST EPSS

CVE-2026-131182 Overview

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store malicious Search Processing Language (SPL) in a shared dashboard. The malicious SPL could run using the permissions of the user who opened the dashboard and could access or modify data available to that user and disrupt Splunk Enterprise availability. The vulnerability is possible because Splunk Enterprise does not preserve quoted search argument boundaries when it processes a dashboard search. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker, a user who holds the "power" Splunk role, should not be able to exploit the vulnerability at will.

Critical Impact

Remote, authenticated attackers who persuade a user to act can exploit this Security Vulnerability in Splunk Enterprise. The CVSS base score is 7.6 (High).

Affected Products

  • Splunk Enterprise: see the vendor advisory for the exact affected versions

Discovery Timeline

  • 2026-11-19: CVE-2026-131182 published to the National Vulnerability Database by psirt@cisco.com
  • 2026-11-19: last updated in the NVD database

Technical Details for CVE-2026-131182

Vulnerability Analysis

CVE-2026-131182 is a Security Vulnerability weakness (CWE-116) in Splunk Enterprise. Based on its CVSS vector, the flaw can be reached over the network, needs some level of access, and relies on a user taking an action.

With a CVSS base score of 7.6, apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Root Cause

The vendor description states: In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store malicious Search Processing Language (SPL) in a shared dashboard. The malicious SPL could run using the permissions of the user who opened the dashboard and could access or modify data available to that user and disrupt Splunk Enterprise availability. The vulnerability is possible because Splunk Enterprise does not preserve quoted search argument boundaries when it processes a dashboard search. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker, a user who holds the "power" Splunk role, should not be able to exploit the vulnerability at will.

Attack Vector

Based on the CVSS vector, the flaw can be reached over the network, needs some level of access, and relies on a user taking an action. Attack complexity is low complexity.

No exploitation in the wild is confirmed by CISA at the time of the last update. Check the references below for any vendor or researcher proof of concept.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L

Detection Methods for CVE-2026-131182

Detection Strategies

  • Inventory every instance of Splunk Enterprise and compare the running version with the affected range above.
  • Check external attack surface scans for internet facing instances of the component.
  • Run an authenticated vulnerability scan once your scanner ships a check for this CVE.

Monitoring Recommendations

  • Forward Splunk Enterprise application, access and audit logs to your SIEM for retrospective hunting.
  • Alert on new processes, configuration changes or outbound connections from the affected service.
  • Track the vendor advisory and the CISA KEV catalog for changes in exploitation status.

How to Mitigate CVE-2026-131182

Immediate Actions Required

  • Apply the fixed version of Splunk Enterprise named in the vendor advisory.
  • Prioritize internet facing and business critical instances first.
  • Rescan after the change to confirm the exposure is closed.

Patch Information

Use the fixed version listed in the vendor advisory for Splunk Enterprise.

Workarounds

  • If patching must wait, restrict network access to the affected service and place it behind authentication or a web application firewall rule.

CWE References

Technical References

This entry is built directly from NVD, CISA KEV and EPSS data. Verify fixed versions in the vendor advisory before you deploy.

Frequently asked questions

CVE-2026-131182 is a high severity Security Vulnerability in Splunk Enterprise with a CVSS score of 7.6. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Related CVEs

CRITICAL9.4
CVE-2025-59158
Coollabs Coolify

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Coolify versions prior to and including v4.0.0-beta.420.6 are vulnerable to a stored cross-site scripting (XSS) attack in the project creation workflow. An authenticated user with low privileges (e.g., member role) can create a project with a maliciously crafted name containing embedded JavaScript. When an administrator later attempts to delete the project or its associated resource, the payload automatically executes in the admin’s browser context. Version 4.0.0-beta.420.7 contains a patch for the issue.

Jan 5, 2026
CRITICAL9.3
CVE-2026-32754
Freescout

FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. Versions 1.8.208 and below are vulnerable to Stored Cross-Site Scripting (XSS) through FreeScout's email notification templates. Incoming email bodies are stored in the database without sanitization and rendered unescaped in outgoing email notifications using Blade's raw output syntax {!! $thread->body !!}. An unauthenticated attacker can exploit this vulnerability by simply sending an email, and when opened by any subscribed agent or admin as part of their normal workflow, enabling universal HTML injection (phishing, tracking) and, in vulnerable email clients, JavaScript execution (session hijacking, credential theft, account takeover) affecting all recipients simultaneously. This issue has been fixed in version 1.8.209.

Mar 19, 2026
CRITICAL9.1
CVE-2026-48358
Adobe Commerce

Adobe Commerce is affected by an Improper Encoding or Escaping of Output vulnerability that could result in arbitrary code execution in the context of the current user. An attacker with high privileges could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.

Jul 14, 2026
HIGH8.8
CVE-2026-104368
Export and Import Users and Customers

The Export and Import Users and Customers plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.7.5 via the plugin's own export and re-import workflow. The vulnerability exists because of a CSV escape-character mismatch between the exporter and the importer: class-csvwriter.php writes cells with fputcsv() using PHP's default backslash (\) escape character, while class-csvreader.php parses the same file with fgetcsv() using a double-quote (") as the escape character. As a result, a crafted value stored in a Subscriber's Biographical Info field — containing a backslash-quote sequence followed by a newline — is written as a single quoted CSV field but parsed back as two separate rows on import. The injected second row is then processed by hf_create_customer() as a new user record whose user_login, user_pass, user_email, and role are entirely attacker-controlled, allowing the creation of an arbitrary Administrator account. This makes it possible for authenticated attackers with Subscriber-level access and above to escalate their privileges to Administrator.

Oct 30, 2026
HIGH8.6
CVE-2026-129100
Cudy TR3000

Cudy TR3000 before 2.5.42 contains a remote code execution vulnerability that allows authenticated administrators to execute commands as root by uploading crafted OpenVPN private or tls-auth keys. Attackers can close the inline key block with </key>, inject directives such as tls-verify that bypass the .ovpn denylist, and have OpenVPN execute the hook as root.

Nov 13, 2026
HIGH8.2
CVE-2026-32811
Dadrus Heimdall

Heimdall is a cloud native Identity Aware Proxy and Access Control Decision service. When using Heimdall in envoy gRPC decision API mode with versions 0.7.0-alpha through 0.17.10, wrong encoding of the query URL string allows rules with non-wildcard path expressions to be bypassed. Envoy splits the requested URL into parts, and sends the parts individually to Heimdall. Although query and path are present in the API, the query field is documented to be always empty and the URL query is included in the path field. The implementation uses go's url library to reconstruct the url which automatically encodes special characters in the path. As a consequence, a parameter like /mypath?foo=bar to Path is escaped into /mypath%3Ffoo=bar. Subsequently, a rule matching /mypath no longer matches and is bypassed. The issue can only lead to unintended access if Heimdall is configured with an "allow all" default rule. Since v0.16.0, Heimdall enforces secure defaults and refuses to start with such a configuration unless this enforcement is explicitly disabled, e.g. via --insecure-skip-secure-default-rule-enforcement or the broader --insecure flag. This issue has been fixed in version 0.17.11.

Mar 20, 2026
Your next credential

Earn your free CTEM certification.

Learn to scope, prioritize, validate and mobilize fixes for CVEs like CVE-2026-131182 with a free CTEM certification.

Free to takePublicly verifiable

Beginner / Practitioner / Program Leader

Explore certifications