Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

Quick assessment

Affected
Splunk Splunk Enterprise
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Splunk Enterprise 版本低于 10.4.3、10.2.7、10.0.10 和 9.4.15 的情况下,拥有具备 能力的角色的用户可以创建一个以句点( )结尾的原生 Splunk 用户名。该漏洞存在的原因是,在将用户名用于用户目录之前,用户名验证机制并未拒绝末尾带句点的用户名。这可能导致不同的原生 Splunk 用户名共享用户级别的配置数据,并且用户管理操作可能会影响错误的账户或导致操作失败。 更多信息请参阅 Splunk 文档中的以下内容: 设置原生 Splunk 认证(https://help

CVSS 4.1 · Medium
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-76277

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Improper Input Validation of Native Splunk Usernames through the REST API in Splunk Enterprise
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
Source: CVE Program / CVE List V5
Vulnerability Type
输入验证不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Splunk Splunk Enterprise 10.4 ~ 10.4.3 -

II. Public POCs for CVE-2026-76277

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-76277

请登录查看更多情报信息。

Other References for CVE-2026-76277 (1)

Same Patch Batch · Splunk · 2026-10-07 · 23 CVEs total

CVE-2026-76268 9.8 CRITICAL Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise
CVE-2026-76266 7.7 HIGH Local Privilege Escalation through Linux Package Upgrades in Splunk Enterprise
CVE-2026-76265 6.5 MEDIUM Improper Access Control through REST API Endpoints in Splunk Secure Gateway
CVE-2026-76274 6.5 MEDIUM Server-Side Request Forgery (SSRF) through the REST API in Splunk App for Splunk Observabi
CVE-2026-76269 6.5 MEDIUM Improper Access Control in Search Job Retrieval through the REST API in Splunk Enterprise
CVE-2026-76270 6.5 MEDIUM Structured Query Language (SQL) Injection in the SPL2 Module Catalog in Splunk Enterprise
CVE-2026-76271 6.5 MEDIUM Denial of Service (DoS) in the Discover Splunk Observability Cloud app for Splunk Enterpri
CVE-2026-76280 6.3 MEDIUM Incorrect Permission Assignment for App Key Value Store Collections in Splunk Secure Gatew
CVE-2026-76286 5.3 MEDIUM Server-Side Request Forgery (SSRF) through Custom API Tools in Splunk MCP Server
CVE-2026-76278 4.3 MEDIUM Authorization Bypass in SPL2 Module Permissions in Splunk Enterprise
CVE-2026-76272 4.3 MEDIUM Missing Access Control through the REST API in Splunk Secure Gateway
CVE-2026-76267 4.3 MEDIUM Log Injection through the REST API in Splunk App for Splunk O11y Cloud
CVE-2026-76264 4.3 MEDIUM Improper Authorization through the REST API in Splunk Enterprise
CVE-2026-76276 4.3 MEDIUM Information Disclosure in the Discover Splunk Observability Cloud app through Splunk Web f
CVE-2026-76275 4.3 MEDIUM Improper Authorization in Search Job Listings through the REST API in Splunk Enterprise
CVE-2026-76273 4.3 MEDIUM Improper Input Validation through the collect Command in Splunk Enterprise
CVE-2026-76279 4.3 MEDIUM Improper Input Validation of Index Names through the collect Command in Splunk Enterprise
CVE-2026-76281 Improper Access Control in Splunk Enterprise
CVE-2026-76284 Improper Neutralization in Splunk Enterprise
CVE-2026-76283 Protection Mechanism Failure in Splunk Enterprise

Showing top 20 of 23 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2026-76277

No comments yet


Leave a comment