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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Splunk | — | Upgrade Splunk Enterprise to version 10.0.12Upgrade Splunk Enterprise to version 10.2.9Upgrade Splunk Enterprise to version 10.4.5Upgrade Splunk Enterprise to version 10.6.1Upgrade Splunk Enterprise to version 9.4.17 | Nov 19, 2026 | Nov 18, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub