CVE-2026-76277
CVE-2026-76277: 1 tracked advisory record across Splunk. Compare vendor sources and published fix guidance.
Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.
Vendor advisory comparison
Splunk
1 advisory- Advisory severityMedium4.1
Medium [CVE-2026-76277] Improper Input Validation of Native Splunk Usernames through the REST API in Splunk Enterprise
CVE-2026-76277Source published Source updated
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 products in this advisory
- Splunk Enterprise
- Source-reported 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
- Source-reported fixed versions
- 10.4.3
- 10.2.7
- 10.0.10
- 9.4.15
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
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.