Splunk SOAR arbitrary file write via path traversal in REST API
Splunk SOAR versions below 8.8.0 are affected, and the fix is available in 8.8.0. CVSS rates it High (8.8).
- Exploited
- No known exploitation
- Fix
- Fixed in 8.8.0
- Who is exposed
- Specific setups only
Summary
Written by a model
In Splunk SOAR versions below 8.8.0, an authenticated user with repository edit access could cause Splunk SOAR to write files outside the configured repository, which lets the user modify files that the user account running Splunk SOAR can write to. The vulnerability is possible because Splunk SOAR does not require source control repository paths to remain inside the configured repository.
Who should check
Teams running Splunk SOAR versions below 8.8.0
“Splunk SOAR 8.8 Below 8.8.0 8.8.0”
What to do
Check whether your setup matches what the bug needs.
Splunk SOAR versions below 8.8.0Upgrade to a fixed version: 8.8.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131270 (Path Traversal through the REST API in Splunk SOAR), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131270 (entry last updated 2026-11-20):
Affected:
- Splunk Splunk SOAR: fixed in 8.8.0
Fixed versions: 8.8.0.
Conditions (all must be true for the bug to be hit):
- Splunk SOAR versions below 8.8.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-131270 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131270 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1108
- https://www.cve.org/CVERecord?id=CVE-2026-131270
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131270
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131270"}.Affected versions
- Splunk Splunk SOARfixed in 8.8.0
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1108 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131270 |
| Record | NVD · CVE-2026-131270 |
Questions about CVE-2026-131270
Is CVE-2026-131270 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
This is a path traversal flaw in the Splunk SOAR REST API, which can let requests reach file paths outside the locations the API is meant to use.
Source: advisory.splunk.com, cve.org
Which versions are affected by CVE-2026-131270?
Splunk SOAR: before 8.8.0.
Source: cve.now feed data
Am I affected, and how do I check?
Splunk SOAR versions below 8.8.0 are affected. To check, compare the installed Splunk SOAR version against 8.8.0 in the product's version information.
Source: advisory.splunk.com, cve.org
How do I fix CVE-2026-131270?
Upgrade Splunk SOAR to version 8.8.0 or higher.
Source: advisory.splunk.com, cve.org
Related
- CVE-2026-131287Remote Code Execution (RCE) through the REST API in Splunk SOAR
- CVE-2026-131295Improper Authorization in Playbook Execution in Splunk SOAR
- CVE-2026-131293Improper Access Control in the Data Management Automation API in Splunk SOAR
- CVE-2026-131297Single Sign-On Authentication Bypass in Splunk SOAR
- CVE-2026-131282Information Exposure through the REST API in Splunk SOAR
- CVE-2026-131288[Flashpoint] Privilege Escalation through HAProxy Cluster Operations in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.