Skip to main content
VulnerabilityPublished

CVE-2026-20260: Splunk SOAR · The software does not neutralize or incorrectly neutralizes output that is written to logs.

Affects Splunk SOARSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 8.5.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.5.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Splunk SOAR to 8.5.0.

Affected software

ProductAffectedFixed in
SplunkSplunk SOARAffected
  • >=8.5 <8.5.0
Fixed in
  • 8.5.0

AI-suggested

If you cannot patch yet, administrators should exercise caution when viewing logs from untrusted sources and consider filtering or sanitizing log data externally to prevent interpretation of control characters.

Description

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.

References

Community reviews

Loading reviews…