Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privileged Splunk account
-
DeliverySend crafted request to affected endpoint
-
ExploitBypass access control (CWE-284)
-
ExecutionReach privileged functionality across scope
-
ImpactFull 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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.
Primary rating from Vendor (cisco).
CVSS VectorVendor: cisco
Lifecycle Timeline
4DescriptionCVE.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
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.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when
curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple t
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
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la
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,
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the
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
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Rated high seve
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t
EUVD-2026-107652
GHSA-vwr2-h35x-mr2c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB