CyberSecBulletin
CVE-2026-76293NVD status: Analyzed

Splunk Enterprise: Improper Control of Generation of Code

Published Updated By the CyberSecBulletin desk

CVE-2026-76293 is a high-severity improper control of generation of code vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists versions 10.4.3, 10.2.8, 10.0.11 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.47% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Splunk Enterprise to 10.4.3 or 10.2.8 or 10.0.11 or 9.4.16, whichever matches your release line, or a later version.
  2. Update Splunk to 9.4.16 or 10.0.11 or 10.2.8 or 10.4.3, whichever matches your release line, or a later version.
  3. Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
SplunkSplunk Enterprise10.4 up to, but not including, 10.4.3; 10.2 up to, but not including, 10.2.8; 10.0 up to, but not including, 10.0.11; 9.4 up to, but not including, 9.4.1610.4.3, 10.2.8, 10.0.11, 9.4.16
SplunkSplunk9.4.0 up to, but not including, 9.4.16; 10.0.0 up to, but not including, 10.0.11; 10.2.0 up to, but not including, 10.2.8; 10.4.0 up to, but not including, 10.4.39.4.16, 10.0.11, 10.2.8, 10.4.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cisco.com).

Official description

In Splunk Enterprise versions below 10.4.3, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_manager_xml capability could execute arbitrary operating-system commands using the permissions of the user account running Splunk Enterprise by opening the affected configuration in the Splunk Web Manager page. The vulnerability is possible because Splunk Web evaluates user-controlled expressions from Manager XML without sufficiently restricting the expression syntax.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Control of Generation of Code

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

How developers prevent this class of flaw

  • Refactor your program so that you do not have to dynamically generate code.
  • Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
  • Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.

More Improper Control of Generation of Code vulnerabilities (CWE-94)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Splunk Enterprise

All Splunk Enterprise vulnerabilities

Recent Improper Control of Generation of Code vulnerabilities

Spotted an error? Tell us.