CVE-2026-131270 — Splunk Splunk SOAR (8.8.0) — CWE-22
CVE-2026-131270 is a HIGH severity Path Traversal & Arbitrary File Read vulnerability (CWE-22) (CVSS 8.8/10) affecting Splunk Splunk SOAR (8.8.0). Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) with zero user interaction (UI:N), resulting in complete compromise of system confidentiality and integrity (C:H/I:H).
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-131270
CVSS 8.8/10 · HIGH · 19.11.2026
CWE: CWE-22
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Path Traversal / LFI
Summary: 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.
Affected: Splunk:Splunk SOAR
⚡ ATTACK CHAIN
1. Test ../../../../etc/passwd in file parameters.
2. URL encode variants: ..%2F, ..%252F, null byte %00.
3. PHP LFI to RCE via log poisoning: inject PHP in User-Agent, include access log.
4. PHP wrappers: php://filter/convert.base64-encode/resource=config.php
🔧 Tools: LFISuite, ffuf, Burp Suite, dotdotpwn
🗺️ MITRE ATT&CK: T1083 (File and Directory Discovery), T1552 (Unsecured Credentials)
🌍 REAL WORLD IMPACT
All confidential data readable/stealable; data can be modified or deleted; service can be completely taken down.
🛡️ REMEDIATION
→ Apply vendor security update for Splunk:Splunk SOAR.
→ Use realpath() canonicalization, implement allowlists.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
⚠️ Planned maintenance (2 weeks).
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]
FOFA Query