Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-76341— Risky Commands Safeguards Bypass through Table Editor Dataset Initial Data in Splunk Enterprise

Quick assessment

Affected
Splunk Splunk Enterprise
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Splunk Enterprise 10.4.2、10.2.6、10.0.9 和 9.4.14 之前的版本中，持有“power”（特权）Splunk 角色的用户可以在“Table Editor”（表格编辑器）数据集中存储攻击者控制的搜索处理语言（SPL），并共享该数据集。当持有“admin”（管理员）Splunk 角色的用户打开该数据集时，会触发该 SPL 命令。由于 SPL 以第二位用户的权限运行，可能导致所有相关数据被泄露，并可在搜索头（search head）上修改部分有限数据。 该漏洞之所以存在，是因为

CVSS 5.4 · Medium EPSS 0.23% · P14

Affected Version Matrix 4

VendorProduct Version RangeStatus
Splunk Splunk Enterprise 10.4< 10.4.2 affected
10.2< 10.2.6 affected
10.0< 10.0.9 affected
9.4< 9.4.14 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-76341

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Risky Commands Safeguards Bypass through Table Editor Dataset Initial Data in Splunk Enterprise
Source: CVE Program / CVE List V5
Vulnerability Description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a Table Editor dataset and share the dataset. A user who holds the "admin" Splunk role triggers the SPL when that user opens the dataset in the Table Editor. The SPL runs using the permissions of the second user and could expose all relevant data and modify limited data on the search head. The vulnerability is possible because the Table Editor does not apply SPL safeguards for risky commands when it prepares the dataset initial data. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who holds the "power" Splunk role should not be able to exploit the vulnerability at will. For more information see Define initial data for a new table dataset (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/9.4/create-and-edit-table-datasets/define-initial-data-for-a-new-table-dataset), SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands), and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制不正确
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Splunk Splunk Enterprise 10.4 ~ 10.4.2 -

II. Public POCs for CVE-2026-76341

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-76341

请登录查看更多情报信息。

Same Patch Batch · Splunk · 2026-08-19 · 110 CVEs total

CVE-2026-76311 9.4 CRITICAL Improper Access Control in Embedded Report Dispatch Archives in Splunk Enterprise
CVE-2026-76310 9.4 CRITICAL Improper Access Control through Embedded Report REST API Requests in Splunk Enterprise
CVE-2026-76312 9.4 CRITICAL Improper Access Control through Embedded Reports in Splunk Enterprise
CVE-2026-76404 9.1 CRITICAL Remote Code Execution (RCE) through Deserialization of Untrusted Data in Splunk MCP Server
CVE-2026-76335 8.8 HIGH Remote Code Execution (RCE) through Splunk Web Manager Configuration in Splunk Enterprise
CVE-2026-76350 8.8 HIGH Improper Privilege Management through PDF Attachments for Email Alert Actions in Splunk En
CVE-2026-76389 8.8 HIGH Server-Side Request Forgery (SSRF) through the REST API in Cisco Talos Intelligence for En
CVE-2026-76319 8.8 HIGH Remote Code Execution (RCE) through Federated Search in Splunk Enterprise
CVE-2026-76351 8.8 HIGH Server-Side Request Forgery (SSRF) through the Report Notification REST API in Splunk Secu
CVE-2026-76395 8.8 HIGH Remote Code Execution (RCE) through Deserialization of Untrusted Data in the Model Loading
CVE-2026-76316 8.8 HIGH Stored SPL Injection through Deployment Server Broker Registration in Splunk Enterprise
CVE-2026-76253 8.8 HIGH Privilege Escalation through Scheduled Search Alert Action Configuration in Splunk Enterpr
CVE-2026-76352 8.8 HIGH Improper Authorization through the REST API in Splunk Enterprise
CVE-2026-76315 8.8 HIGH Code Injection through Splunk Web Manager Configuration in Splunk Enterprise
CVE-2026-76259 8.8 HIGH Improper Privilege Management on the Management Port in Splunk Enterprise for Windows
CVE-2026-76317 8.8 HIGH Path Traversal through the Lookup Configuration REST API in Splunk Enterprise
CVE-2026-76314 8.8 HIGH Remote Code Execution (RCE) through Splunk Web Manager Configuration in Splunk Enterprise
CVE-2026-76313 8.8 HIGH Remote Code Execution (RCE) through the REST API in Splunk Enterprise
CVE-2026-76394 8.3 HIGH Missing Authorization in Container and Connection Management through the REST API in Splun
CVE-2026-76391 8.3 HIGH Improper Privilege Management through Agent Run History in Splunk AI Toolkit

Showing top 20 of 110 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: Splunk Enterprise
Same vendor: Splunk
Same weakness: CWE-863

V. Comments for CVE-2026-76341

No comments yet

Leave a comment