CVE Tools

CVE-2026-20297

Path Traversal through 'explicit_appname' in the App Install REST Endpoint in Splunk Enterprise

No known exploitation. EPSS puts it in the 46th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Splunk Cloud PlatformAffected: ≥ 10.5.2605, < 10.5.2605.0Upgrade to: 10.5.2605.0Affected: ≥ 10.4.2604, < 10.4.2604.6Upgrade to: 10.4.2604.6Affected: ≥ 10.2.2510, < 10.2.2510.18Upgrade to: 10.2.2510.18Affected: ≥ 10.1.2507, < 10.1.2507.24Upgrade to: 10.1.2507.24Stated by: CVE record
  • Splunk EnterpriseAffected: ≥ 10.4, < 10.4.1Upgrade to: 10.4.1Affected: ≥ 10.2, < 10.2.5Upgrade to: 10.2.5Affected: ≥ 10.0, < 10.0.8Upgrade to: 10.0.8Affected: ≥ 9.4, < 9.4.13Upgrade to: 9.4.13 + 1 more branchStated by: CVE record
  • SplunkAffected: ≥ 9.3.0, < 9.3.14Upgrade to: 9.3.14Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS46th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 46th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 9 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Record updated
  4. Publishedweakness classified, att&ck mapped, record updated

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Scored 7.2 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required HighRequires admin or elevated privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Splunk, not every advisory.