The CVSS 7.2 score here is misleading. Yes, you need edit_local_apps AND install_apps to exploit this — but in Splunk's operational model, these capabilities are routinely bundled for anyone who deploys apps, which is a baseline Splunk operator function. You're not measuring an attacker pool of specialists; you're measuring a configuration state that Splunk's own workflow design encourages. The path traversal then does something the CVSS anchor doesn't capture: it collapses Splunk's entire directory isolation in one step. $SPLUNK_HOME/etc/ contains the authentication configuration, user definitions, password stores from local apps, and the app manifest files Splunk trusts at runtime. This isn't a lateral movement step — it's already filesystem sovereignty. The 'legitimate app installation' phrasing in the description is the real signal: the attack looks exactly like normal admin activity, which is why no alerting rule catches it. The 2019 path traversal in app installation (CVE-2019-10018) suggests this may be incomplete remediation from a surgical fix rather than an architectural one. Compounding the problem: Splunk's audit logging records 'app installed successfully' but not the individual file paths written during installation. Even organizations with comprehensive Splunk logging have no first-party evidence trail for detection or reconstruction. This means compensating controls must focus on file integrity monitoring of $SPLUNK_HOME/etc/ rather than Splunk-native logging. The unresolved question that changes the post-exploitation narrative: can you overwrite existing files in $SPLUNK_HOME/etc/ or only write to previously nonexistent paths? This determines whether authentication configuration replacement is direct or requires planted files plus a Splunk restart.
CVE-2026-20297
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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 the news
Third-party coverage- Splunk, Zoom Patch Critical Vulnerabilities - SecurityWeek
- Weekly Recap: WordPress RCE, SonicWall 0-Days, AI Service ...
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in Splunk Enterprise and Cloud Platform allows users with both `edit_local_apps` and `install_apps` capabilities to install apps outside the intended app directory, writing files to `$SPLUNK_HOME/etc/` and its subdirectories. This occurs due to insufficient path validation in the app installation workflow, potentially allowing privilege escalation or deployment of malicious configurations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 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>= 10.1.2507, < 10.1.2507.24>= 10.2.2510, < 10.2.2510.18>= 10.4.2604, < 10.4.2604.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Splunk Enterprise versionRun: $SPLUNK_HOME/bin/splunk version (or via web UI: Settings > About > Version)Affected if Version is 9.3.0 through 9.3.13, 9.4.0 through 9.4.12, 10.0.0 through 10.0.7, 10.2.0 through 10.2.4, or exactly 10.4.0
-
Check Splunk Cloud Platform versionNavigate to: Settings > Account > Subscription info (or contact Splunk Cloud admin)Affected if Version starts with 10.1.2507.x where x < 24, or 10.2.2510.x where x < 18, or 10.4.2604.x where x < 6
-
Identify roles or users with install_apps capabilityGo to Settings > Users and Roles > Roles, or run: | rest /services/authorization/roles | search capabilities=install_appsAffected if Any roles have the install_apps capability assigned
-
Identify roles or users with edit_local_apps capabilityGo to Settings > Users and Roles > Roles, or run: | rest /services/authorization/roles | search capabilities=edit_local_appsAffected if Any roles have the edit_local_apps capability assigned
-
Find roles with BOTH capabilitiesCross-reference results from steps 3 and 4. A role with both capabilities can trigger the vulnerability.Affected if A single role or user account has BOTH edit_local_apps AND install_apps capabilities enabled
You are affected if your Splunk version falls within any of the affected ranges AND you have users or roles with both the edit_local_apps and install_apps capabilities assigned.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.3.149.4.1310.0.8
Upgrade Splunk Enterprise to versions 10.4.1, 10.2.5, 10.0.8, 9.4.13, or 9.3.14 and above, or upgrade Splunk Cloud Platform to the fixed versions for respective release tracks. Alternatively, restrict the `edit_local_apps` and `install_apps` capabilities to only trusted administrative users until patching can be completed.
Splunk Enterprise: 10.4.1, 10.2.5, 10.0.8, 9.4.13, or 9.3.14 (depending on current branch); Splunk Cloud Platform: 10.5.2605.0, 10.4.2604.6, 10.2.2510.18, or 10.1.2507.24
- 1. Identify the current Splunk Enterprise or Splunk Cloud Platform version by checking $SPLUNK_HOME/etc/splunk.version or the About page in Splunk Web
- 2. For Splunk Enterprise: upgrade to version 10.4.1 (or 10.2.5, 10.0.8 if on those branches), or 9.4.13/9.3.14 for older branches
- 3. For Splunk Cloud Platform: upgrade to version 10.5.2605.0, 10.4.2604.6, 10.2.2510.18, or 10.1.2507.24 based on your current track
- 4. Prior to upgrade, create a full backup of $SPLUNK_HOME including etc/ and var/ directories
- 5. Follow Splunk's official upgrade documentation for your deployment type (single instance, distributed, or cloud)
- 6. After upgrade, audit $SPLUNK_HOME/etc/ for any unexpected files that may have been written during prior vulnerable app installations
- 7. Verify the fix by attempting a test app installation and confirming files are written only to the intended app directory
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThe CVSS 7.2 score here is misleading. Yes, you need `edit_local_apps` AND `install_apps` to exploit this — but in Splunk's operational model, these capabilities are routinely bundled for anyone who deploys apps, which is a baseline Splunk operator function. You're not measuring an attacker pool of specialists; you're measuring a configuration state that Splunk's own workflow design encourages. The path traversal then does something the CVSS anchor doesn't capture: it collapses Splunk's entire directory isolation in one step. `$SPLUNK_HOME/etc/` contains the authentication configuration, user definitions, password stores from local apps, and the app manifest files Splunk trusts at runtime. This isn't a lateral movement step — it's already filesystem sovereignty. The 'legitimate app installation' phrasing in the description is the real signal: the attack looks exactly like normal admin activity, which is why no alerting rule catches it. The 2019 path traversal in app installation (CVE-2019-10018) suggests this may be incomplete remediation from a surgical fix rather than an architectural one. Compounding the problem: Splunk's audit logging records 'app installed successfully' but not the individual file paths written during installation. Even organizations with comprehensive Splunk logging have no first-party evidence trail for detection or reconstruction. This means compensating controls must focus on file integrity monitoring of `$SPLUNK_HOME/etc/` rather than Splunk-native logging. The unresolved question that changes the post-exploitation narrative: can you overwrite existing files in `$SPLUNK_HOME/etc/` or only write to previously nonexistent paths? This determines whether authentication configuration replacement is direct or requires planted files plus a Splunk restart.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-20297 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data