Skip to main content
CVE-2026-76545VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76545· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium · fixed in 10.6.1 : update Splunk Enterprise when convenient.

Data as of 19 Nov 2026, 22:19 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisco)CVSS 3.16.5
Patch
Available – fixed in 10.6.1, 10.4.5, 10.2.9 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.6 <10.6.1
Fixed in
  • 10.6.1
SplunkSplunk EnterpriseAffected
  • >=10.4 <10.4.5
Fixed in
  • 10.4.5
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.9
Fixed in
  • 10.2.9
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.12
Fixed in
  • 10.0.12
SplunkSplunk EnterpriseAffected
  • >=9.4 <9.4.17
Fixed in
  • 9.4.17

AI-suggested

A fix is available in Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17. Users should upgrade to one of these versions to remediate the vulnerability. No vendor advisory content was provided to indicate otherwise.

Description

Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where an unauthenticated user can enumerate valid usernames via the REST API or Splunk Web. This is due to differing login failure responses for locked accounts versus nonexistent usernames. Additionally, repeated login attempts can lock out existing user accounts.

References

Community reviews

Loading reviews…