CVE-2026-20296 is a high-severity cross-site request forgery vulnerability in the Deployment Server functionality of Splunk Web. Deployment Server endpoints accept GET requests without CSRF-token validation, and caller-controlled input is insufficiently neutralized before inclusion in a Search Processing Language (SPL) search. An attacker can induce a user holding the list_deployment_server capability to issue a crafted browser request, causing arbitrary SPL searches to execute in the splunk-system-user context. Affected releases include Splunk Enterprise versions earlier than 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and specified affected Splunk Cloud Platform release lines before their respective fixed versions.
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.
14 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 Enterprise CSRF vulnerability in the Deployment Server that can let an attacker trick a user with the list_deployment_server capability into executing arbitrary SPL as splunk-system-user, exposing stored credentials and indexed data.
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.