CVE-2026-76270 is a SQL injection vulnerability in SPL2 module catalog filtering caused by failure to parameterize user-supplied values before incorporating them into database queries. A user whose role includes the list_spl2_modules capability can exploit filtering to access all relevant data exposed through the affected REST API, including private SPL2 module definitions belonging to other users. Splunk Enterprise 10.4.x releases before 10.4.3 are affected; the 10.2.x, 10.0.x, and 9.4.x branches are unaffected. Splunk Cloud Platform is also identified as having the vulnerable query handling, but affected Cloud versions are unspecified.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.