Skip to content
VulniPulse
Advisory severityMedium4.1Splunk

Medium [CVE-2026-76277] Improper Input Validation of Native Splunk Usernames through the REST API in Splunk Enterprise

This medium-severity Splunk advisory covers CVE-2026-76277 affecting Splunk Enterprise.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-76277 Source published Source updated

VulniPulse record published

Affected products & platforms
SplunkSplunk Enterprise
Open source advisory

Android app · Google Play

Monitor future Splunk CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user that holds a role with the edit_user capability could create a native Splunk username that ends with a period. The vulnerability is possible because username validation does not reject a trailing period before the username is used for a user directory.

This can cause distinct native Splunk usernames to share per-user configuration data, and user-management operations can affect the wrong account or fail. For more information see Set up native Splunk authentication ( ) and Define roles on the Splunk platform with capabilities ( ) in the Splunk documentation.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.3
  • Splunk Enterprise 10.2 before 10.2.7
  • Splunk Enterprise 10.0 before 10.0.10
  • Splunk Enterprise 9.4 before 9.4.15

Official advisory · high-confidence parse· fetched 1 day ago·verify at source

Fixed versions
  • 10.4.3
  • 10.2.7
  • 10.0.10
  • 9.4.15

Official advisory · high-confidence parse· fetched 1 day ago·verify at source

Mitigation

Upgrade to a fixed release: 10.4.3, 10.2.7, 10.0.10, 9.4.15. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 1 day ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.