Skip to content
VulniPulse
Medium6.5Splunk

CVE-2026-131186: Path Traversal in Deployment Server Remote Input Listing in Splunk Enterprise

This Splunk advisory covers CVE-2026-131186 in Splunk Enterprise.

Open the Splunk advisory

Key facts

Vendor rating
Medium, CVSS 6.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N · base score 6.5, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.
Weakness
  • CWE-22 The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location
CISA KEV
Not listed (catalogue checked )
Affected
Splunk Enterprise 10.4 before 10.4.5; Splunk Enterprise 10.2 before 10.2.9; Splunk Enterprise 10.0 before 10.0.12 and 1 more below
Fixed in
10.4.5, 10.2.9, 10.0.12 and 1 more below
Source published
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

SplunkSplunk Enterprise

Description

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user that holds a role with the list_deployment_server capability could access sensitive information from inputs.conf files outside the intended deployment app directory through the Representational State Transfer (REST) API.

The vulnerability is possible because the REST API does not restrict a deployment app name to an existing deployment app before reading input configurations. For more information see authorize.conf ( ), Deployment server architecture ( ), and inputs.conf ( ) in the Splunk documentation.

Text from the source record.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.5
  • Splunk Enterprise 10.2 before 10.2.9
  • Splunk Enterprise 10.0 before 10.0.12
  • Splunk Enterprise 9.4 before 9.4.17

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-131186

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • For more information see authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.4-configuration-file-reference/authorize.conf), Deployment server architecture (https://help.splunk.com/en/splunk-enterprise/administer/update-your-deployment/9.0/deployment-server-and-forwarder-management/deployment-server-architecture), and inputs.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/configuration-file-reference/9.4.16-configuration-file-reference/inputs.conf) in the Splunk documentation.

Workarounds

  • The vulnerability is possible because the REST API does not restrict a deployment app name to an existing deployment app before reading input configurations.

Support dates for the fixed release lines

All end-of-life dates for Splunk Enterprise

Splunk advisories, November 2026All Splunk advisories

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.

Alert me about Splunk Enterprise