Skip to main content

Splunk Enterprise CVE-2026-76299

| EUVDEUVD-2026-107652 CRITICAL
Improper Access Control (CWE-284)
2026-10-21 cisco GHSA-vwr2-h35x-mr2c
9.9
CVSS 3.1 · Vendor: cisco
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privileged Splunk account
  2. Delivery
    Send crafted request to affected endpoint
  3. Exploit
    Bypass access control (CWE-284)
  4. Execution
    Reach privileged functionality across scope
  5. Impact
    Full compromise of confidentiality, integrity, availability

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a low-privileged but authenticated Splunk Enterprise account (CVSS PR:L), reachable over the network with no user interaction. The advisory does not name a specific feature, protocol, SAPI, or configuration setting, so the exact trigger is not described in the available sources. Limiting factors: exploitation is gated by needing valid (even if low-privilege) authentication to the Splunk Enterprise instance and by running an affected version - Splunk Enterprise 9.4 before 9.4.16, 10.0 before 10.0.11, 10.2 before 10.2.8, or 10.4 before 10.4.4; instances already upgraded to those fixed releases are not exploitable. No non-default configuration is stated as required.

Impact

Signals point in a consistently high-priority direction, though they rest on thin vendor disclosure. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, base 9.9) describes a network-reachable, low-complexity flaw that needs only a low-privileged account, requires no user interaction, and crosses a security scope boundary with total confidentiality, integrity, and availability impact - the profile of a privilege-escalation or authentication/access-control bypass. The vuln.today decision label is act_now, and a vendor patch is available. However, key corroborating signals are MISSING rather than conflicting: no EPSS exploitation probability is provided, the input does not list CISA KEV status (treated as not listed), and there is no PoC or exploit reference. Therefore exploitation is characterized as 'no public exploit identified at time of analysis' - the high score reflects severity and potential, not confirmed real-world abuse. One data caveat: the description is verbatim Cisco 'internal security hardening review' boilerplate, yet the CPE, affected-version list, references, and advisory (Splunk SVD-2026-1008) all identify the product as Splunk Enterprise; Cisco owns Splunk, so this is consistent, but the description adds no technical detail about the actual Splunk flaw. Net: a credible high-priority issue warranting prompt patching per the act_now label, with the caveat that its urgency is driven by CVSS severity and vendor prioritization rather than observed exploitation.

Exploit ScenarioDerived

An attacker holding a low-privileged authenticated Splunk Enterprise account sends network requests that abuse an improper access-control weakness (CWE-284) to reach functionality or data outside their authorization boundary, consistent with the scope-change and authentication-bypass characterization. Because the advisory does not describe the trigger, the precise request or feature abused is not detailed in available sources. No public exploit code or PoC reference is provided at the time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 22, 2026

Improper access control in Splunk Enterprise 9.4, 10.0, 10.2, and 10.4 allows a low-privileged authenticated user to cross a security boundary and achieve high confidentiality, integrity, and availability impact, making the release a 9.9 severity fix. The flaw was found during Cisco's internal hardening review rather than through external reporting, and the affected ranges are 9.4 before 9.4.16, 10.0 before 10.0.11, 10.2 before 10.2.8, and 10.4 before 10.4.4. No public exploit code has been identified and there is no CISA KEV entry, but vendor patch availability combined with an act_now priority label places upgraded discipline on anyone running an unpatched instance; the trigger is not described in the available sources.

RemediationAI

Splunk has released fixed builds for every affected branch: upgrade to Splunk Enterprise 9.4.16, 10.0.11, 10.2.8, or 10.4.4 depending on the branch in use, per vendor advisory SVD-2026-1008 at https://advisory.splunk.com/advisories/SVD-2026-1008; vendor-released patch: 9.4.16, 10.0.11, 10.2.8, 10.4.4. Because this CVE is one item in a cumulative software hardening release addressing multiple internally discovered access-control defects, confirm with the advisory that the chosen build contains the full set of related fixes rather than only this record. The available sources document no workaround or configuration-level mitigation, so updating is the only complete fix; any interim reduction in exposure would have to come from narrowing who holds even low-privileged accounts and from limiting which networks can reach the Splunk web and REST interfaces, neither of which is a substitute for the patched release.

Affected VersionsENISA

Splunk Enterprise 9.4 <9.4.16
Splunk Enterprise 10.0 <10.0.11
Splunk Enterprise 10.4 <10.4.4
Splunk Enterprise 10.2 <10.2.8

Affected Packages

euvd splunk_enterprise fix: 9.4.16, 10.0.11, 10.2.8, 10.4.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Splunk Enterprise is a data collection, indexing, and analytics platform (widely deployed as a SIEM) whose security model rests on role-based access controls over search, index, and administrative objects exposed through the web interface and REST API. This entry is classified under CWE-284 (Improper Access Control), meaning the authorization logic fails to constrain an actor to the resources or actions their role permits, rather than a flaw in cryptography or input handling. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H is notable for its Scope:Changed component: the vulnerable component's authorization failure is assessed to impact resources beyond its own security scope, which is consistent with a low-privileged account reaching data or functionality intended to be out of reach. The public tag set labels this an authentication bypass, but the scored vector requires credentials (PR:L), so the observed defect is better characterised as a privilege or boundary bypass available to an already-authenticated low-privileged user than as pre-authentication access. The vendor advisory does not name the affected feature, protocol, SAPI endpoint, or configuration setting, so the exact trigger and the specific objects reachable are not described in the available sources and should be treated as unconfirmed pending the full SVD-2026-1008 text. Affected product identification is anchored by the CPE cpe:2.3:a:splunk:splunk_enterprise, and no non-default configuration is stated as a prerequisite, implying default deployments on affected versions are in scope.

Know when Splunk gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cisco) PRIMARY 9.9 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.9 CRITICAL

Network-reachable access-control bypass needing only a low-privileged account (PR:L), no user interaction, crossing a scope boundary (S:C) with full C/I/A impact; trigger undocumented so AC kept low per vendor vector.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L

Primary rating from Vendor (cisco).

CVSS VectorVendor: cisco

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 22, 2026 - 14:22 NVD
9.9 (CRITICAL)
Patch available
Oct 22, 2026 - 02:16 EUVD
CVE Published
Oct 21, 2026 - 22:52 cve.org
CRITICAL 9.9
CVE Published
Oct 21, 2026 - 22:52 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-76299 are related to improper access control and are grouped under the Common Weakness Enumeration (CWE) CWE-284.

Executive ViewAI

Why It Matters

Splunk Enterprise versions 9.4, 10.0, 10.2, and 10.4 contain a critical improper access control vulnerability (CVE-2026-76299) that allows a low-privileged authenticated user to cross a security boundary and compromise confidentiality, integrity, and availability (CVSS 9.9). Splunk is widely deployed for security monitoring and log management, so exploitation could enable data exfiltration, tampering with security events, or disruption of monitoring-directly impacting the organization's ability to detect and respond to threats. Leadership should prioritize patching because the flaw was found during internal hardening and requires an authenticated user, but it still poses a high risk if unpatched instances exist with low-privileged accounts.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
High
widely deployed enterprise SIEM/log platform in large organizations
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Splunk

View all
CVE-2014-0160 HIGH POC
7.5 Apr 07

The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe

CVE-2026-20253 CRITICAL POC
9.8 Jun 10

Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.

CVE-2021-22901 HIGH POC
8.1 Jun 11

curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when

CVE-2022-32206 MEDIUM POC
6.5 Jul 07

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple t

CVE-2024-36985 HIGH POC
8.8 Jul 01

In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or powe

CVE-2023-46214 HIGH POC
8.8 Nov 16

In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la

CVE-2023-32707 HIGH POC
8.8 Jun 01

In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100,

CVE-2022-43571 HIGH POC
8.8 Nov 03

In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t

CVE-2022-32207 CRITICAL POC
9.8 Jul 07

When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the

CVE-2022-35737 HIGH POC
7.5 Aug 03

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a

CVE-2022-43551 HIGH POC
7.5 Dec 23

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Rated high seve

CVE-2022-32221 CRITICAL POC
9.8 Dec 05

When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy