CVE-2022-32154: Cross-origin risky SPL command injection in Splunk Enterprise dashboards
- Vendor
- Splunk
CVE-2022-32154 is a vulnerability in Splunk Enterprise dashboards affecting versions prior to 9.0. A browser-based attacker can inject risky Search Processing Language (SPL) commands into a dashboard form token when that token is incorporated into a query during a cross-origin request. This condition can bypass Splunk SPL safeguards intended to restrict execution of custom or potentially dangerous commands. The issue is rooted in insufficient neutralization of untrusted input flowing from dashboard form tokens into search queries in a cross-origin context, enabling manipulation of the resulting SPL beyond intended restrictions.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can allow execution of risky SPL commands that would otherwise be constrained by SPL safeguards. Depending on the commands available and the victim user's effective permissions, this can enable unauthorized search activity, access to sensitive data, data exfiltration, deletion or tampering of indexed data, and execution of actions that materially weaken monitoring integrity. Because exploitation is browser-based, impact is generally realized in the security context of the targeted user's authenticated Splunk session rather than as unauthenticated direct server-side compromise.
Mitigation
If you can’t patch tonight, do this now.
Until patched, reduce exposure by restricting cross-origin interactions with Splunk, limiting which users can access dashboards that embed form tokens into searches, and minimizing assignment of capabilities that permit risky SPL commands. Review and harden dashboards that pass token values into queries, and monitor audit search activity for anomalous use of risky commands such as deletion, scripted actions, or export-oriented operations.
Remediation
Patch, then assume compromise.
Upgrade Splunk Enterprise to version 9.0 or later, where this issue is addressed. Review dashboards that incorporate form tokens into queries and validate that untrusted token values cannot influence risky command execution paths. Apply Splunk's controls for limiting access to custom and potentially risky commands so that even if query manipulation is attempted, exposed capabilities are minimized.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2022-32154 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2022-32154 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2022-32154?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2022-32154.
- Is there a patch for CVE-2022-32154?
- Upgrade Splunk Enterprise to version 9.0 or later, where this issue is addressed. Review dashboards that incorporate form tokens into queries and validate that untrusted token values cannot influence risky command execution paths.
- What products are affected by CVE-2022-32154?
- Splunk and Splunk Cloud Platform.
- How severe is CVE-2022-32154?
- CVE-2022-32154 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 1.3% (70th percentile) as of Oct 16, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.