EUVD-2026-36087
GHSA-7m5m-884p-fv5r
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
ANSI escape code injection in Splunk SOAR versions below 8.5.0 allows an unauthenticated remote attacker to embed terminal control sequences into application log files via crafted HTTP request paths. When an administrator subsequently views those logs in a terminal emulator, the escape codes may be interpreted, enabling visual output manipulation such as overwriting displayed text, hiding log entries, or altering terminal state. No public exploit code has been identified at time of analysis, and exploitation requires administrator interaction with affected log output, keeping real-world risk moderate despite the low authentication barrier.
Technical ContextAI
Splunk SOAR is an enterprise security orchestration and automation platform. The vulnerability arises from CWE-117 (Improper Output Neutralization for Logs), where the application fails to strip or escape ANSI control sequences - character sequences beginning with ESC (0x1B) followed by bracket characters - from HTTP request path strings before writing them to application log files. Terminal emulators such as xterm, GNOME Terminal, and iTerm2 interpret these sequences to control cursor position, text color, and display formatting. An attacker controlling the request path can therefore inject sequences that, when rendered, may overwrite prior log lines, blank sections of the log, or alter terminal behavior for the viewing session. The affected CPE is cpe:2.3:a:splunk:splunk_soar:*:*:*:*:*:*:*:*, covering all Splunk SOAR versions prior to 8.5.0 across all platforms.
RemediationAI
The primary remediation is upgrading Splunk SOAR to version 8.5.0 or later, which introduces sanitization of control characters from HTTP request paths prior to log writes. The fix version of 8.5.0 is inferred from the description stating affected versions are 'below 8.5.0'; consult the official Splunk advisory at https://advisory.splunk.com/advisories/SVD-2026-0611 for confirmed patch release details and upgrade procedures. As a compensating control where immediate upgrade is not feasible, administrators should avoid reviewing SOAR application logs directly in terminal emulators; instead, use log management platforms (e.g., Splunk Enterprise, a SIEM) that render log content as plain text and strip or display raw escape sequences safely. Additionally, restricting network access to the SOAR HTTP interface to trusted IP ranges reduces the attacker's ability to inject malicious request paths. Note that these workarounds do not eliminate the injection path - they only reduce exposure by limiting log review in vulnerable contexts.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or powe
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100,
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functional
When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly re
A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an atta
Same weakness CWE-117 – Improper Output Neutralization for Logs
View allSame technique Code Injection
View allShare
External POC / Exploit Code
Leaving vuln.today