In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could determine whether a username exists through the Representational State Transfer (REST) API or Splunk Web and lock out existing user accounts through repeated login attempts.
The vulnerability is possible because Splunk Enterprise returns different login failure responses for locked existing user accounts and nonexistent usernames.
The vulnerability is possible because Splunk Enterprise returns different login failure responses for locked existing user accounts and nonexistent usernames.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.
Workaround
No workaround given by the vendor.
References
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1103 |
|
History
Thu, 19 Nov 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could determine whether a username exists through the Representational State Transfer (REST) API or Splunk Web and lock out existing user accounts through repeated login attempts. The vulnerability is possible because Splunk Enterprise returns different login failure responses for locked existing user accounts and nonexistent usernames. | |
| Title | Information Disclosure through the REST API and Splunk Web in Splunk Enterprise | |
| Weaknesses | CWE-204 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-11-19T19:55:28.655Z
Reserved: 2026-08-19T12:02:03.644Z
Link: CVE-2026-76545
No data.
Status : Received
Published: 2026-11-19T20:17:53.980
Modified: 2026-11-19T20:17:53.980
Link: CVE-2026-76545
No data.
OpenCVE Enrichment
No data.
Weaknesses