CVE-2026-76338
Last modified
CVE-2026-76338 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has access to a trusted distributed search private key could forge an administrative session token, access all relevant data, affect system integrity, and disrupt service availability. The vulnerability is possible because the distributed search authentication token endpoint does not require a signed request to identify a configured search peer, allowing the request to fall back to shared local key material. EPSS estimates a 0.27% chance of exploitation in the next 30 days.
Description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has access to a trusted distributed search private key could forge an administrative session token, access all relevant data, affect system integrity, and disrupt service availability. The vulnerability is possible because the distributed search authentication token endpoint does not require a signed request to identify a configured search peer, allowing the request to fall back to shared local key material. For more information see About distributed search (https://help.splunk.com/en/splunk-enterprise/administer/distributed-search/10.4/overview-of-distributed-search/about-distributed-search) and authentication.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.2-configuration-file-reference/authentication.conf) in Splunk documentation.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk | >= 9.4.0, < 9.4.14 |
| Splunk | Splunk | >= 10.0.0, < 10.0.9 |
| Splunk | Splunk | >= 10.2.0, < 10.2.6 |
| Splunk | Splunk | >= 10.4.0, < 10.4.2 |
References
- https://advisory.splunk.com/advisories/SVD-2026-0801Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-76338?
How severe is CVE-2026-76338?
How do I fix CVE-2026-76338?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-76332In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.1
- CVE-2026-76333In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.1
- CVE-2026-76334In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …6.4
- CVE-2026-76335In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-76336In Splunk Enterprise versions below 10.4.2 and 10.2.6, a use…7.1
- CVE-2026-76337In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …5.3
- CVE-2026-76339In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …5.4
- CVE-2026-7634The SlimStat Analytics plugin for WordPress is vulnerable to…7.2
- CVE-2026-76340In Splunk Enterprise 10.4 versions below 10.4.2, an unauthen…5.3
- CVE-2026-76341In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …5.4
- CVE-2026-76342In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …5.4
- CVE-2026-76343In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …6.5
Are you affected by CVE-2026-76338?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
