← Search CVEs

CVE-2026-76277

MEDIUM 4.1

Published 2026-10-07 · Last modified 2026-10-08

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 (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/use-the-native-splunk-platform-authentication-scheme/set-up-native-splunk-authentication) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

NO EXPLOITATION SIGNALS

No known exploitation, public exploit, or elevated probability at this time. Track for changes.

Exploitation likelihood

0.2%chance of exploitation in 30 days · 16th percentile

○ In CISA KEV ○ Catalogued PoC

Impact if exploited

4.1CVSS 3.1 · MEDIUM

  • ConfidentialityLow
  • IntegrityLow
  • AvailabilityLow

What an attacker needs

  • ✓Access: Reachable over the network — no local access needed
  • ⚠Privileges: Requires an admin / high-privilege account
  • ✓User interaction: No user interaction needed
  • ⚠Complexity: Needs a race window or specific setup

✓ lowers the bar for an attacker · ⚠ raises it

Proof of concept

No public PoC is currently catalogued.

Search for new PoCs

Search GitHub now — results may be empty or unverified.

Tracked sources are checked daily for recent CVEs, including PoCs published after the original disclosure. A later release appears after a tracked source lists it and a refresh succeeds.

Data snapshot:

Affected

Vendors Splunk

Products Splunk Enterprise Splunk

Weakness (CWE)

  • CWE-20: The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

References and research data (JSON)

Known Affected Software Configurations

VendorProductVersion range
SplunkSplunk≥ 9.4.0 and < 9.4.15
SplunkSplunk≥ 10.0.0 and < 10.0.10
SplunkSplunk≥ 10.2.0 and < 10.2.7
SplunkSplunk≥ 10.4.0 and < 10.4.3

All CVSS metrics

  • MEDIUM 4.1 v3.1 · CNA Primary
    CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
  • MEDIUM 4.1 v3.1 · NVD Secondary
    CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

References

Advisories

Sources: NVD · CVE.org · EPSS