Read the docs
TI-2026-69301 Aliases CVE-2026-76277GHSA-f49j-g49x-qqr9

Splunk Enterprise accepts native usernames ending with a period

Priority LOW 19CWE-20Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
Low · Low · Low
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

Splunk Enterprise is affected in versions from 10.4 before 10.4.3, from 10.2 before 10.2.7, from 10.0 before 10.0.10, and from 9.4 before 9.4.15. Username validation does not reject a trailing period (CWE-20), so a user with a role that holds the edit_user capability can create a native Splunk username ending with a period. Distinct usernames can then share per-user configuration data, and user-management operations can affect the wrong account or fail.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00244 15th percentileScored 2026-11-07
Fix Fixed Splunk Enterprise (Splunk): 10.4.3, 10.2.7, 10.0.10 +1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
SplunkSplunk Enterprise10.4 to before 10.4.3; 10.2 to before 10.2.7; 10.0 to before 10.0.10; 9.4 to before 9.4.1510.4.3, 10.2.7, 10.0.10, 9.4.15Patch availableCNA
  • Splunk Enterprise VendorSplunk Affected 10.4 to before 10.4.3; 10.2 to before 10.2.7; 10.0 to before 10.0.10; 9.4 to before 9.4.15 Fixed in 10.4.3, 10.2.7, 10.0.10, 9.4.15 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*9.4.0 to before 9.4.15; 10.0.0 to before 10.0.10; 10.2.0 to before 10.2.7; 10.4.0 to before 10.4.3VulnerableSplunk
  • cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* Versions 9.4.0 to before 9.4.15; 10.0.0 to before 10.0.10; 10.2.0 to before 10.2.7; 10.4.0 to before 10.4.3 Vulnerable ·Splunk

Remediation

Upgrade Splunk Enterprise to 10.4.3 on the 10.4 line, 10.2.7 on the 10.2 line, 10.0.10 on the 10.0 line, or 9.4.15 on the 9.4 line.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

  • Fix · CNA Splunk Enterprise (Splunk) Fixed in 10.4.3, 10.2.7, 10.0.10, 9.4.15

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Splunk Enterprise 10.0.10, 10.2.7 and 2 more versions

    14 records Highest priority Priority MEDIUM 3 MEDIUM, 11 LOW

    Other records, highest priority first

    • TI-2026-69309 Coding standard flaws in Splunk Enterprise allow remote attacksPriority MEDIUM 49
    • TI-2026-69308 Improper Neutralization in Splunk EnterprisePriority MEDIUM 49
    • TI-2026-69306 Resource lifetime control flaw in Splunk EnterprisePriority MEDIUM 40
    Show all 14 records →

Timeline

  1. 2026-10-07 Threatist record created from CVE-2026-76277
  2. 2026-10-07 Alias added: GHSA-f49j-g49x-qqr9
  3. 2026-10-08 CISA SSVC decision points changed

References

Advisory 1

  • TI-2026-16444 Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-00154 The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly… KEVCVSS 3.1HIGH 7.5
  • TI-2023-24841 Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing CVSS 3.1HIGH 8.8
  • TI-2023-15979 ‘edit_user’ Capability Privilege Escalation CVSS 3.1HIGH 8.8
  • TI-2024-30707 Remote Code Execution (RCE) due to insecure session storage configuration in Splunk Enterprise on Windows CVSS 3.1HIGH 8.8
  • TI-2022-21345 Reflected Cross-Site Scripting via the radio template in Splunk Enterprise CVSS 3.1HIGH 8.8
See all 297 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences