CVE-2026-20297 remediation guide

Splunk Splunk Enterprise, Splunk Cloud Platform, splunk

In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, 9.4.13, and 9.3.14, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.2.2510.18, and 10.1.2507.24, a user who holds a role that contains the `edit_local_apps` and `install_apps` capabilities could cause a legitimate app installation to write files outside the intended app directory, into `$SPLUNK_HOME/etc/` and its subdirectories.<br><br>The vulnerability is caused by a path traversal in the app installation workflow, which does not restrict the installation path to the intended app directory.

Open CVE record

ProductSplunk Splunk Enterprise, Splunk Cloud Platform, splunk

Affected versions>= 10.4 < 10.4.1, >= 10.2 < 10.2.5, >= 10.0 < 10.0.8, >= 9.4 < 9.4.13, >= 9.3 < 9.3.14, >= 10.5.2605 < 10.5.2605.0, >= 10.4.2604 < 10.4.2604.6, >= 10.2.2510 < 10.2.2510.18, >= 10.1.2507 < 10.1.2507.24, >= 9.3.0 < 9.3.14, >= 9.4.0 < 9.4.13, >= 10.0.0 < 10.0.8, >= 10.2.0 < 10.2.5, 10.4.0

Fixed versions9.3.14, 9.4.13, 10.0.8, 10.2.5, 10.1.2507.24, 10.2.2510.18, 10.4.2604.6

Priority basisReview · CVSS 7.2 · EPSS 0.48%

Identify the affected asset

Confirm whether Splunk Splunk Enterprise, Splunk Cloud Platform, splunk is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 10.4 < 10.4.1, >= 10.2 < 10.2.5, >= 10.0 < 10.0.8, >= 9.4 < 9.4.13, >= 9.3 < 9.3.14, >= 10.5.2605 < 10.5.2605.0, >= 10.4.2604 < 10.4.2604.6, >= 10.2.2510 < 10.2.2510.18, >= 10.1.2507 < 10.1.2507.24, >= 9.3.0 < 9.3.14, >= 9.4.0 < 9.4.13, >= 10.0.0 < 10.0.8, >= 10.2.0 < 10.2.5, 10.4.0. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 9.3.14, 9.4.13, 10.0.8, 10.2.5, 10.1.2507.24, 10.2.2510.18, 10.4.2604.6. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.