CVE-2026-76545
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 …
Impact
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.
An attacker can exploit this over the network, without logging in, without any action by a user. If it succeeds: low risk of data being read, low risk of outages.
Affected products · Splunk
| Product | Affected versions |
|---|---|
| Splunk Enterprise | from 10.6 before 10.6.1 from 10.4 before 10.4.5 from 10.2 before 10.2.9 from 10.0 before 10.0.12 from 9.4 before 9.4.17 |