Loading vulnerability…
CVE-2026-20296 is a high-severity vulnerability in the Deployment Server functionality of Splunk Web affecting Splunk Enterprise and Splunk Cloud Platform. The flaw allows an attacker to induce a user who holds a role with the list_deployment_server capability to execute arbitrary Search Processing Language (SPL) searches on the attacker’s behalf. Those searches run as splunk-system-user, rather than with the victim’s normal effective privileges. The issue arises from two conditions: Deployment Server endpoints in Splunk Web fail to validate CSRF tokens on GET requests, and caller-controlled input is not properly neutralized before being incorporated into an SPL search. Together, these weaknesses enable a CSRF-driven safeguard bypass that can be used to submit attacker-influenced SPL through a victim’s browser session.
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.
splunk-system-user. This can expose indexed data and stored credentials, producing high confidentiality impact and high integrity impact, with limited availability impact. Because the searches execute in the context of a powerful internal system user, the attacker can bypass intended command safeguards and gain access to data that would not normally be available through the victim’s ordinary session context.If you can’t patch tonight, do this now.
list_deployment_server capability to only users who strictly require it and limiting opportunities for those users to be targeted with phishing or malicious web content.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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity command safeguards bypass vulnerability in Splunk products that could allow attackers to access credentials and data.
A high-severity Splunk Web Deployment Server vulnerability that can let an unauthenticated attacker, via phishing and user interaction, execute arbitrary SPL searches as splunk-system-user and expose indexed data and stored credentials.
A high-severity Splunk vulnerability caused by CSRF protection bypass on Deployment Server GET requests combined with improper neutralization of caller-supplied input, allowing arbitrary SPL searches to run as `splunk-system-user` and potentially exposing stored credentials and indexed data.
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.