Skip to main content
Mallory
CriticalVulnerability

CVE-2026-76299: Improper Access Control in Splunk Enterprise

Published Oct 21, 2026 · Updated 22 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days12 mentions · peak 5 in a dayToday
CVSS9.9Critical · v3.1
EPSS0.33%26th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-76299CWE-284 · Improper Access Control

CVE-2026-76299 groups multiple internally discovered improper access control vulnerabilities in Splunk Enterprise under CWE-284. The findings were addressed in the October 2026 security hardening release associated with advisory SVD-2026-1008. The highest CVSS v3.1 score among the grouped findings is 9.9, rated Critical. Affected releases include 10.4.0–10.4.3, 10.2.0–10.2.7, 10.0.0–10.0.10, and 9.4.0–9.4.15. Specific vulnerable components, functions, exploitation mechanisms, and detailed consequences have not been disclosed.

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.

The vulnerabilities concern failures to enforce access controls, potentially allowing unauthorized access to protected resources or functionality. The specific resources affected and resulting confidentiality, integrity, and availability impacts are currently not available. The grouped findings have a maximum CVSS v3.1 score of 9.9; this does not establish a specific impact for every finding.

Mitigation

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

No vulnerability-specific temporary workaround has been disclosed. Reviewing exposed interfaces and restricting user permissions may reduce general exposure but are not established mitigations for these findings and do not replace upgrading.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise 10.4.x to 10.4.4 or later, 10.2.x to 10.2.8 or later, 10.0.x to 10.0.11 or later, or 9.4.x to 9.4.16 or later within the corresponding branch. Apply the security hardening fixes identified in advisory SVD-2026-1008.

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.
FAQ

Frequently asked questions

Is CVE-2026-76299 exploited in the wild?
As of Oct 28, 2026, Mallory has no reports of CVE-2026-76299 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76299?
As of Oct 28, 2026, Mallory has found no public exploit for CVE-2026-76299.
Is there a patch for CVE-2026-76299?
Upgrade Splunk Enterprise 10.4.x to 10.4.4 or later, 10.2.x to 10.2.8 or later, 10.0.x to 10.0.11 or later, or 9.4.x to 9.4.16 or later within the corresponding branch. Apply the security hardening fixes identified in advisory SVD-2026-1008.
How severe is CVE-2026-76299?
CVE-2026-76299 has a CVSS v3.1 score of 9.9 (Critical) and an EPSS score of 0.33% (26th percentile) as of Oct 28, 2026.
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 activity5Community discussion across Reddit, Mastodon, and other social sources.