Loading vulnerability…
CVE-2026-20260 affects Splunk SOAR versions below 8.5.0. The vulnerability arises because SOAR does not strip or neutralize control characters from HTTP request paths before writing those paths to application log files. An unauthenticated attacker can send a specially crafted HTTP request whose path contains ANSI escape sequences. When those log entries are later viewed by an administrator in a terminal emulator that interprets ANSI control codes, the injected sequences may be executed by the terminal for display control purposes. This is a log injection / output neutralization failure in which untrusted request data is recorded without sanitization, enabling terminal escape sequence injection into logs.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.