CVE-2026-20260
In Splunk SOAR (Security Orchestration, Automation, and Response) versions below 8.5.0, an unauthenticated attacker could inject American National Standards Institute (ANSI) escape codes into SOAR application log files through specially crafted HTTP request paths, which a terminal emulator might interpret when an administrator views the logs.<br><br>The injection is possible because SOAR does not strip control characters from HTTP request paths before writing them to application logs.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 4.3
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- EPSS probability
- 0.20%
- CWE
- CWE-117
- Published
- 2026-06-10
- Last modified
- 2026-06-10
Affected products
- Splunk Splunk SOAR
Weakness type
Related vulnerabilities
- CVE-2026-14350 — Vulnerabilities exists in IBM Cloud Pak for Data System
- CVE-2026-9736 — Vulnerabilities exists in IBM Netezza Software
- CVE-2026-15603 — morgan vulnerable to Log Forging via unescaped Unicode line separators
- CVE-2026-81696 — openssl_encrypt before 1.4.9 Terminal Injection via info Command
- CVE-2026-81695 — openssl_encrypt before 1.4.9 Terminal Injection via key_id
- CVE-2026-81694 — verify-usb before 1.4.9 Output Injection via Unsanitized Filenames
- CVE-2026-54511 — @logtape/syslog: syslog log injection via unescaped control characters and unvalidated SD-NAME keys
- CVE-2026-44256 — Wazuh: CRLF Log Injection via Unsanitized Basic-Auth Username