On this page (7 sections)

A critical vulnerability, tracked as CVE-2026-131202, affects Splunk Enterprise Security versions below 8.7.0. According to the NVD record, a user who holds the "ess_admin" Splunk Enterprise Security role could execute arbitrary code on the search head, running as the account that runs Splunk Enterprise. The flaw involves two features: lookup file upload and the Configuration Checker.

Anyone who runs Splunk Enterprise Security, especially teams that hand out the ess_admin role widely or run Splunk under a privileged operating system account, should review this. The advisory is new, and the research so far comes from a single advisory chain, so some details are still unconfirmed.

What happened

On November 19, 2026, the vulnerability was published through the National Vulnerability Database and then mirrored in the GitHub Advisory Database. The vendor advisory is referenced as SVD-2026-1106 on Splunk's advisory site. The research we have does not include the text of that advisory, so this article relies on the CVE description.

The description names two underlying weaknesses: Splunk Enterprise Security does not restrict lookup upload file types, and it does not keep Configuration Checker module paths within the intended directory. It says a user with the ess_admin role could combine the lookup file upload and Configuration Checker functionality to execute arbitrary code on the search head.

Technical details in plain terms

The weakness is classified as CWE-22, commonly called path traversal. This happens when an application builds a file path from input it does not fully control, and the path can end up pointing outside the folder the developer meant to confine it to. In this case the description says the Configuration Checker's module paths are not kept within the intended directory.

The second weakness is that lookup uploads are not limited by file type. A lookup is meant to be a data table, but the description says the product does not restrict what types can be uploaded. The description states that these two gaps can be combined to reach code execution as the user account running Splunk Enterprise. It does not spell out the exact sequence, and we are not describing exploitation steps.

How serious is the score?

The CVSS vector lists network attack vector, low complexity, no user interaction, and high impact on confidentiality, integrity and availability, with a changed scope. The key brake is privileges required: high. An attacker needs an account that already holds the ess_admin role. That makes this less of an internet-wide drive-by risk and more of a privilege escalation and insider or stolen-credential risk.

Who is exposed

  • Organizations running Splunk Enterprise Security below 8.7.0.
  • Environments where several people or service accounts hold the ess_admin role.
  • Setups where the operating system account running Splunk has broad access, since code runs as that account.
  • Teams whose Splunk web interface is reachable from untrusted networks, because the attack vector is rated as network.

If nobody untrusted holds ess_admin and the role is tightly controlled, practical risk is lower, but a single phished or reused admin credential could be enough to reach the flaw. Search heads often sit close to sensitive log data and credentials, so the impact of code execution there can be large.

The GitHub entry lists patched versions as unknown, and the research does not say whether exploitation has been seen. Check the Splunk advisory SVD-2026-1106 for the authoritative fixed version and any workarounds.

How to check your exposure

First find your Enterprise Security version. In Splunk Web, the app listing under Apps, Manage Apps shows the installed version of Splunk Enterprise Security. Then review who holds the ess_admin role.

This read-only REST search, run in the Splunk search bar on the search head by an administrator, lists users and their roles so you can spot who has ess_admin. It only reads configuration and changes nothing. Look for accounts you do not recognize or that no longer need the role.

List Splunk users and their roles (run in the Splunk search bar as an admin)Text
| rest /services/authentication/users splunk_server=local
| table title roles

Also review recent lookup uploads and any unusual files in lookup and app directories, and check audit logs for Configuration Checker activity from accounts that do not normally use it. The research gives no specific indicators of compromise, so treat unexpected files or activity as a reason to investigate rather than as proof.

What to do now

  1. Identify every Splunk Enterprise Security instance and note its version.
  2. Read Splunk advisory SVD-2026-1106 for the fixed version and any vendor guidance.
  3. Plan and apply the upgrade to Enterprise Security 8.7.0 or later, following Splunk's documented upgrade process.
  4. Until you upgrade, reduce the ess_admin role to the smallest set of trusted people and remove unused accounts.
  5. Enforce strong, unique passwords and multi-factor or single sign-on for accounts holding ess_admin.
  6. Confirm the operating system account running Splunk has only the permissions it needs.
  7. Restrict network access to the Splunk web interface to trusted management networks.
  8. Review lookup uploads and audit logs for anything unexpected since the role was granted.
Caution. Upgrading Splunk Enterprise Security can involve restarts and affects searches and correlation rules. Test in a non-production environment where possible, back up your configuration, and schedule a maintenance window.
Tip. The Splunk documentation linked in the CVE, Users and roles for Splunk Enterprise Security, explains what the ess_admin role covers and is a good basis for a role review.

Detection and monitoring afterwards

Because exploitation needs a privileged account, watch for the signs of one being misused: new or recently changed ess_admin assignments, logins from unfamiliar addresses, and lookup uploads of file types that are not normally used. Alert on child processes started by the Splunk service account that are not part of normal operation.

If you expose any Splunk interface to the internet, outside-in monitoring helps you notice unexpected changes to what is reachable. Webforta Monitor tracks uptime, certificates, DNS and header changes, and the Webforta scanner runs read-only checks of sites you verify. Neither detects or fixes this specific flaw, so patching and role hygiene remain the actual remedy. For broader background on limiting exposure, see what a WAF is and our small business website security guide.

What we know and do not know

  • Confirmed by the CVE description: affected versions below 8.7.0, the ess_admin precondition, the two contributing weaknesses, and code execution as the Splunk account.
  • Unconfirmed in our research: exact patched version beyond the implication of 8.7.0, any workaround, and whether anyone has exploited this.
  • Independence: the NVD and GitHub entries carry the same text, and only one advisory chain is covered so far, so treat details as preliminary until Splunk's own advisory is reviewed.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-131202 - GitHub Advisory Databasegithub.com
  2. CVE-2026-131202: In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_admin" Splunk Enterprise Security role could execute arbitrary code on the…nvd.nist.gov ·
  • Splunk
  • CVE-2026-131202
  • Remote code execution
  • Path traversal
  • SIEM