CVE-2026-76283: Splunk Enterprise · The product does not use or incorrectly uses a protection mechanism that provides sufficient defense
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 7.6 High · fixed in 10.4.3 : patch Splunk Enterprise soon.
Data as of 21 Nov 2026, 17:35 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 7.6 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.3, 10.2.7, 10.0.10 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.3, 10.2.7, 10.0.10 or 9.4.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Fixed versions are available: 10.4.3, 10.2.7, 10.0.10, and 9.4.15. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated beyond applying the official patches.
Description
CVE-2026-76283 is a high-severity vulnerability in Splunk Enterprise involving failure or incorrect use of protection mechanisms (CWE-693). It affects multiple versions prior to fixed releases and can lead to high confidentiality impact, low integrity impact, and high availability impact. The issue was addressed by Splunk in software hardening releases.