Loading vulnerability…
CVE-2026-76281 groups multiple internally identified improper access control vulnerabilities in Splunk Enterprise under CWE-284. Affected release ranges are 10.4.0–10.4.2, 10.2.0–10.2.6, 10.0.0–10.0.9, and 9.4.0–9.4.14. These weaknesses could permit unauthorized access to protected resources or functionality. Specific vulnerable functions, exploitation mechanisms, and individual consequences have not been disclosed.
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.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An access-control vulnerability grouping in Splunk Enterprise, identified in hardening advisory SVD-2026-1002, with a maximum severity score of 9.8. The advisory covers internally identified weaknesses fixed in releases 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The content does not detail the individual mechanisms, exploitation prerequisites, or exact affected-version ranges for this CVE.
An improper access control vulnerability advisory affecting Splunk Enterprise. The advisory describes internally identified vulnerabilities grouped by CWE, with one CVE assigned to each group. Fixes are reported in versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15; specific exploitation mechanisms, impact, and affected version ranges are not provided.
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.