CVE-2026-76262: Splunk Enterprise · The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 10.4.2 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 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 17 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Splunk Enterprise versions 10.4.2 and later include a fix for this vulnerability. Users should upgrade to version 10.4.2 or later to remediate the issue. Since this is not a cloud service, remediation requires applying the official patch. No other mitigation steps are indicated in the vendor advisory.
Description
CVE-2026-76262 is an information disclosure vulnerability in Splunk Enterprise versions 10.4 up to but not including 10.4.2. It allows unauthenticated users to access Prometheus service metrics from the Edge Processor SPL2 Preview sidecar without authentication. This exposure reveals runtime and build metadata of the sidecar. Versions prior to 10.4 are not affected. The vulnerability arises because the Prometheus metrics endpoint lacks authentication, permitting any client able to reach the sidecar to retrieve sensitive metrics data without credentials.