In Splunk Enterprise versions below 10.6.1, 10.4.5, and 10.2.9, a low-privileged user who does not hold the "admin" or
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium · fixed in 10.6.1 : update Splunk Enterprise when convenient.
Data as of 19 Nov 2026, 22:55 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 10.6.1, 10.4.5, 10.2.9
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 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 19 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.6.1, 10.4.5 or 10.2.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to Splunk Enterprise REST API endpoints and review user role assignments to minimize exposure.
Description
A vulnerability in Splunk Enterprise versions below 10.6.1, 10.4.5, and 10.2.9 allows low-privileged users without admin or power roles to access file path and metadata listings from search head knowledge bundles via the REST API. This unauthorized access exposes sensitive metadata such as usernames, private configuration file names, application directories, and security-sensitive file paths. The issue arises because the REST API uses a capability assigned to the 'user' role instead of requiring higher privileges.