Skip to content
VulniPulse
High7.2Splunk

High [CVE-2026-20297] Path Traversal through 'explicit_appname' in the App Install REST Endpoint in Splunk Enterprise

This high-severity Splunk advisory covers CVE-2026-20297 affecting Splunk Enterprise, Splunk Cloud Platform.

CVE-2026-20297 Published Jul 15, 2026Updated by vendor Jul 15, 2026
Affected products & platforms
SplunkSplunk EnterpriseSplunk Cloud Platform
Open vendor advisory

Android app · Google Play

Monitor future Splunk CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

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.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.1
  • Splunk Enterprise 10.2 before 10.2.5
  • Splunk Enterprise 10.0 before 10.0.8
  • Splunk Enterprise 9.4 before 9.4.13
  • Splunk Enterprise 9.3 before 9.3.14
  • Splunk Cloud Platform 10.5.2605 before 10.5.2605.0
  • Splunk Cloud Platform 10.4.2604 before 10.4.2604.6
  • Splunk Cloud Platform 10.2.2510 before 10.2.2510.18
  • Splunk Cloud Platform 10.1.2507 before 10.1.2507.24

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 10.4.1
  • 10.2.5
  • 10.0.8
  • 9.4.13
  • 9.3.14
  • 10.5.2605.0
  • 10.4.2604.6
  • 10.2.2510.18
  • 10.1.2507.24

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Temporary workarounds
  • 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.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.