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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-76387— SPL Injection through the REST API in Splunk Enterprise Security

Quick assessment

Affected
Splunk Splunk Enterprise Security
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 Security是美国Splunk公司的一款企业级安全防护软件。 Splunk Enterprise Security 8.6.1之前版本存在安全漏洞,该漏洞源于Analyst Queue搜索过滤器处理未验证过滤器字段名,可能导致持有mc_investigation_read能力的用户注入Search Processing Language(SPL),从而访问所有相关数据和系统完整性。

CVSS 8.1 · High EPSS 0.40% · P32

Affected Version Matrix 1

VendorProduct Version RangeStatus
Splunk Splunk Enterprise Security 8.6< 8.6.1 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-76387

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
SPL Injection through the REST API in Splunk Enterprise Security
Source: CVE Program / CVE List V5
Vulnerability Description
In Splunk Enterprise Security versions below 8.6.1, a user who holds a Splunk Enterprise Security role that contains the mc_investigation_read capability could inject Search Processing Language (SPL) through Analyst Queue search filters, allowing for access to all relevant data and system integrity available to the scheduled searches that run for that user. The vulnerability is possible because the Analyst Queue search filter handling does not validate filter field names before the fields are included in SPL searches. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.4/installation/users-and-roles-for-splunk-enterprise-security), Manage analyst workflows using the analyst queue in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/mission-control/manage-analyst-workflows-using-the-analyst-queue-in-splunk-enterprise-security), and Overview of Mission Control in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.5/mission-control/overview-of-mission-control-in-splunk-enterprise-security) in the Splunk documentation.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
输入验证不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
Splunk Enterprise Security 输入验证错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Splunk Enterprise Security是美国Splunk公司的一款企业级安全防护软件。 Splunk Enterprise Security 8.6.1之前版本存在安全漏洞,该漏洞源于Analyst Queue搜索过滤器处理未验证过滤器字段名,可能导致持有mc_investigation_read能力的用户注入Search Processing Language(SPL),从而访问所有相关数据和系统完整性。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Splunk Splunk Enterprise Security 8.6 ~ 8.6.1 -

II. Public POCs for CVE-2026-76387

# 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-76387

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

Vendor Advisories for CVE-2026-76387 (1)

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

CVE-2026-76312 9.4 CRITICAL Improper Access Control through Embedded Reports in Splunk Enterprise
CVE-2026-76310 9.4 CRITICAL Improper Access Control through Embedded Report REST API Requests in Splunk Enterprise
CVE-2026-76311 9.4 CRITICAL Improper Access Control in Embedded Report Dispatch Archives 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-76317 8.8 HIGH Path Traversal through the Lookup Configuration REST API in Splunk Enterprise
CVE-2026-76389 8.8 HIGH Server-Side Request Forgery (SSRF) through the REST API in Cisco Talos Intelligence for En
CVE-2026-76350 8.8 HIGH Improper Privilege Management through PDF Attachments for Email Alert Actions in Splunk En
CVE-2026-76319 8.8 HIGH Remote Code Execution (RCE) through Federated Search in Splunk Enterprise
CVE-2026-76259 8.8 HIGH Improper Privilege Management on the Management Port in Splunk Enterprise for Windows
CVE-2026-76314 8.8 HIGH Remote Code Execution (RCE) through Splunk Web Manager Configuration 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-76313 8.8 HIGH Remote Code Execution (RCE) through the REST API in Splunk Enterprise
CVE-2026-76352 8.8 HIGH Improper Authorization through the REST API in Splunk Enterprise
CVE-2026-76253 8.8 HIGH Privilege Escalation through Scheduled Search Alert Action Configuration in Splunk Enterpr
CVE-2026-76315 8.8 HIGH Code Injection through Splunk Web Manager Configuration in Splunk Enterprise
CVE-2026-76391 8.3 HIGH Improper Privilege Management through Agent Run History in Splunk AI Toolkit
CVE-2026-76394 8.3 HIGH Missing Authorization in Container and Connection Management through the REST API in Splun

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

IV. Related Vulnerabilities

V. Comments for CVE-2026-76387

No comments yet


Leave a comment