Loading vulnerability…
CVE-2026-76272 is a missing-authorization vulnerability in Splunk Secure Gateway. The gateway does not verify whether a user is authorized to request a signature, allowing an authenticated Splunk user without the admin or power role to obtain signatures for attacker-controlled payloads. Affected releases include Splunk Enterprise versions before 10.4.3, 10.2.7, 10.0.10, and 9.4.15 in their respective branches, and Splunk Secure Gateway versions before 3.10.11, 3.9.25, and 3.8.72 in their respective branches.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Missing-access-control vulnerability in Splunk Secure Gateway allowing users without admin or power roles to obtain signatures on attacker-controlled payloads. CVSS 4.3. The report identifies fixed Enterprise releases as 10.4.3, 10.2.7, 10.0.10, and 9.4.15, and recommends disabling or removing unused Secure Gateway installations as a compensating control.
An authorization-check vulnerability in Splunk Secure Gateway allows a user without the Splunk admin or power role to obtain signatures for attacker-controlled payloads. The advisory identifies affected Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, and Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72. It does not describe exploitation activity or explicitly confirm patch availability.
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.