Skip to main content
Mallory
MediumVulnerability

CVE-2026-76295: Dashboard and report filter injection in Splunk Secure Gateway

Published Oct 21, 2026 · Updated 19 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 3 in a dayToday
CVSS4.3Medium · v3.1
EPSS0.28%21st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Splunk
IdentifiersCVE-2026-76295CWE-943 · Improper Neutralization of Special…

CVE-2026-76295 is a filter-injection vulnerability in Splunk Secure Gateway caused by failure to neutralize special characters in values used to construct dashboard and report request filters. An authenticated user without the admin or power roles can manipulate filter scope to retrieve additional dashboard and report listings. Returned objects remain limited to those the user is already authorized to access. Affected release branches include Splunk Enterprise versions before 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and Splunk Secure Gateway versions before 3.10.12, 3.9.26, and 3.8.73, respectively.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation bypasses the requested dashboard and report listing filters, exposing listings outside the intended filter scope. It does not bypass underlying object-access permissions: results remain restricted to objects the authenticated user can already access. The vulnerability has a reported CVSS v3 score of 4.3.

Mitigation

If you can’t patch tonight, do this now.

If patching must be delayed, consider disabling unused Splunk Secure Gateway functionality after reviewing operational dependencies. No vulnerability-specific temporary workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to 10.4.4, 10.2.8, 10.0.11, or 9.4.16, or a later fixed release in the corresponding branch. Also upgrade affected Splunk Secure Gateway installations to 3.10.12, 3.9.26, or 3.8.73, or a later fixed release in the corresponding branch.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SplunkSplunkapplication
SplunkSplunk Secure Gatewayapplication
FAQ

Frequently asked questions

Is CVE-2026-76295 exploited in the wild?
As of Oct 30, 2026, Mallory has no reports of CVE-2026-76295 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76295?
As of Oct 30, 2026, Mallory has found no public exploit for CVE-2026-76295.
Is there a patch for CVE-2026-76295?
Upgrade Splunk Enterprise to 10.4.4, 10.2.8, 10.0.11, or 9.4.16, or a later fixed release in the corresponding branch. Also upgrade affected Splunk Secure Gateway installations to 3.10.12, 3.9.26, or 3.8.73, or a later fixed release in the corresponding branch.
What products are affected by CVE-2026-76295?
Splunk and Splunk Secure Gateway.
How severe is CVE-2026-76295?
CVE-2026-76295 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 0.28% (21st percentile) as of Oct 30, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.