Splunk Enterprise up to 9.4.15/10.0.10/10.2.7/10.4.3 resource control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 2.04 |
Summary
A vulnerability identified as very critical has been detected in Splunk Enterprise up to 9.4.15/10.0.10/10.2.7/10.4.3. This vulnerability affects unknown code. The manipulation leads to resource control. This vulnerability is documented as CVE-2026-76300. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Splunk Enterprise up to 9.4.15/10.0.10/10.2.7/10.4.3 and classified as very critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a resource control vulnerability. Using CWE to declare the problem leads to CWE-664. The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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-76300 are related to improper control of a resource through its lifetime and are grouped under the Common Weakness Enumeration (CWE) CWE-664.
The advisory is shared at advisory.splunk.com. The identification of this vulnerability is CVE-2026-76300 since 08/19/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/22/2026).
Upgrading to version 9.4.16, 10.0.11, 10.2.8 or 10.4.4 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 9.4.0
- 9.4.1
- 9.4.2
- 9.4.3
- 9.4.4
- 9.4.5
- 9.4.6
- 9.4.7
- 9.4.8
- 9.4.9
- 9.4.10
- 9.4.11
- 9.4.12
- 9.4.13
- 9.4.14
- 9.4.15
- 10.0.0
- 10.0.1
- 10.0.2
- 10.0.3
- 10.0.4
- 10.0.5
- 10.0.6
- 10.0.7
- 10.0.8
- 10.0.9
- 10.0.10
- 10.2.0
- 10.2.1
- 10.2.2
- 10.2.3
- 10.2.4
- 10.2.5
- 10.2.6
- 10.2.7
- 10.4.0
- 10.4.1
- 10.4.2
- 10.4.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Resource controlCWE: CWE-664
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Enterprise 9.4.16/10.0.11/10.2.8/10.4.4
Timeline
08/19/2026 CVE reserved10/21/2026 VulDB entry created
10/22/2026 Advisory disclosed
10/22/2026 VulDB entry last update
Sources
Advisory: advisory.splunk.comStatus: Confirmed
CVE: CVE-2026-76300 (🔒)
GCVE (CVE): GCVE-0-2026-76300
GCVE (VulDB): GCVE-100-425021
Entry
Created: 10/22/2026 01:06Changes: 10/22/2026 01:06 (54)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.