CVE-2026-76545
Medium 6.5No known exploitationFix availableInformation Disclosure through the REST API and Splunk Web in Splunk Enterprise
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 14% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-204
Patching and mitigation
- Patch status
- Fix available (source: CVE record (cisco))
- Fix documented (source date)
- Vendor solution
- Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Splunk | Splunk Enterprise | from 10.0 before 10.0.12 | 10.0.12 | CVE Program |
| Splunk | Splunk Enterprise | from 10.2 before 10.2.9 | 10.2.9 | CVE Program |
| Splunk | Splunk Enterprise | from 10.4 before 10.4.5 | 10.4.5 | CVE Program |
| Splunk | Splunk Enterprise | from 10.6 before 10.6.1 | 10.6.1 | CVE Program |
| Splunk | Splunk Enterprise | from 9.4 before 9.4.17 | 9.4.17 | CVE Program |
Timeline
Disclosure
CVE record published by cisco
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (cisco)