CVE-2026-131187: Sensitive Information Disclosure through Knowledge Bundle Replication in Splunk Enterprise
This Splunk advisory covers CVE-2026-131187 in Splunk Enterprise.
- CVE-2026-131187
Key facts
- Vendor rating
- Medium, CVSS 4.3
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N· base score 4.3, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: low. Integrity impact: none. Availability impact: none.- Weakness
- CWE-863 The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Splunk Enterprise 10.6 before 10.6.1; Splunk Enterprise 10.4 before 10.4.5; Splunk Enterprise 10.2 before 10.2.9
- Fixed in
- Splunk Enterprise 10.6.1, Splunk Enterprise 10.4.5, Splunk Enterprise 10.2.9 and 2 more below
- Source published
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
In Splunk Enterprise versions below 10.6.1, 10.4.5, and 10.2.9, a low-privileged user who does not hold the "admin" or "power" Splunk roles could access file path and metadata listings from search head knowledge bundles via the Representational State Transfer (REST) API.
This unauthorized access could expose sensitive metadata, including Splunk platform usernames, private knowledge-object configuration file names, installed application directories, and the file path names of security-sensitive configuration and key files.
The vulnerability is possible because the REST API actions that list bundle contents and denied files use a capability available to the "user" role instead of requiring distributed-search administration capabilities. For more information see Knowledge bundle replication overview ( ) in the Splunk documentation.
For more information see Define roles on the Splunk platform with capabilities ( ) in the Splunk documentation.
Text from the source record.
- Splunk Enterprise 10.6 before 10.6.1
- Splunk Enterprise 10.4 before 10.4.5
- Splunk Enterprise 10.2 before 10.2.9
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-131187
Upgrade to a fixed release named by Splunk:
- Splunk Enterprise 10.6.1
- Splunk Enterprise 10.4.5
- Splunk Enterprise 10.2.9
- Splunk Enterprise 10.0.12
- Splunk Enterprise 9.4.17
Vendor guidance
- Upgrade to a fixed release: Splunk Enterprise 10.6.1, Splunk Enterprise 10.4.5, Splunk Enterprise 10.2.9, Splunk Enterprise 10.0.12, Splunk Enterprise 9.4.17.
Support dates for the fixed release lines
- Splunk Enterprise 10.4: support ends
- Splunk Enterprise 10.2: support ends
- Splunk Enterprise 10.0: support ends
- Splunk Enterprise 9.4: support ends
More Splunk advisories
CVE-2026-131197Nov 19, 2026Privilege Escalation through Splunk Web Dashboards in Splunk App for Splunk ObservabilityCVE-2026-131196Nov 19, 2026Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk EnterpriseCVE-2026-131195Nov 19, 2026Denial of Service (DoS) through HTTP PubSub Channel Subscriptions in Splunk EnterpriseCVE-2026-131194Nov 19, 2026Stored Cross-Site Scripting (XSS) through Splunk Web Views in Splunk EnterpriseCVE-2026-131193Nov 19, 2026Improper Input Validation through HTTP Event Collector Token Names in Splunk EnterpriseCVE-2026-131192Nov 19, 2026Authentication Bypass through the REST API in Splunk Enterprise
Get an email when Splunk Enterprise publishes the next one.
See Splunk Enterprise's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.