Critical CVSS 9.9 Security news
Splunk fixes 139 flaws: critical authentication bypass in Enterprise via an empty shared key, code execution in SOAR
On 18 November 2026 Splunk published advisories covering 139 flaws in Splunk Enterprise, Enterprise Security and SOAR. The two worst, in Enterprise, let an unauthenticated attacker run searches or change cluster settings when the server has an empty pass4SymmKey shared secret. SOAR and Enterprise Security get critical post-authentication code execution fixes. No exploitation has been reported. Here is what to patch and what to configure right now.
Key points
- Affected: Splunk Enterprise 9.4 through 10.6, Enterprise Security and App for PCI Compliance below 8.7.0, and Splunk SOAR below 8.8.0.
- Worst flaws: CVE-2026-76536 (CVSS 9.4) and CVE-2026-76535 (9.1) – Splunk accepts an empty shared secret, so an attacker without credentials can change cluster configuration or run SPL searches as a user.
- Post-authentication code execution: SOAR CVE-2026-131253 (9.9) and CVE-2026-131287 (9.6), Enterprise Security CVE-2026-131202 (9.1, ess_admin role).
- Exploited: no. What to do: patch, and set pass4SymmKey until you can; for the dozens of SPL injection flaws, only the update helps.
What happened
On 18 November 2026 Splunk published its quarterly batch of security advisories. They cover 139 first-party flaws: 38 in Splunk Enterprise (SVD-2026-1103), 42 in Enterprise Security and the App for PCI Compliance (SVD-2026-1106) and 59 in Splunk SOAR (SVD-2026-1108). Separate advisories cover the Stream and AI Assistant apps and third-party library updates.
For admins, the pair of critical Enterprise flaws that need no authentication matters most. Both come down to Splunk accepting an empty pass4SymmKey shared secret, and both have a workaround that does not require an upgrade. Splunk does not mention exploitation.
Technical details
| CVE | Product | CVSS 3.1 | Flaw type | Condition |
|---|---|---|---|---|
| CVE-2026-76536 | Enterprise | 9.4 | authentication bypass in the cluster configuration REST API | unauthenticated; standalone instance with clustering disabled and an empty secret |
| CVE-2026-76535 | Enterprise | 9.1 | authentication bypass in the RapidDiag REST API | unauthenticated; empty shared secret – attacker runs SPL as an authenticated user |
| CVE-2026-131253 | SOAR | 9.9 | code execution via the App Wizard | authenticated user who can edit apps and containers and execute playbooks |
| CVE-2026-131287 | SOAR | 9.6 | code execution via the REST API | playbook permissions, cross-repository playbook references and a reused deleted repository name |
| CVE-2026-131202 | Enterprise Security | 9.1 | code execution via REST API path traversal | ess_admin role; lookup file upload combined with Configuration Checker |
SPL injection dominates the 13 high-severity Enterprise flaws: a low-privileged user (not admin or power) can run searches with elevated privileges through the REST API, metric alerts, saved searches or data model acceleration. With CVE-2026-76544, Splunk says this extends to reading stored credentials in cleartext. Other unauthenticated issues: CVE-2026-131192 (CVSS 7.5) exposes indexing-pipeline data when the secret is empty, CVE-2026-131190 (7.5) accepts a factory-default key in parts of RapidDiag, and CVE-2026-131196 (7.5) crashes splunkd via Splunk-to-Splunk data receiving. We do not describe how to exploit them.
Who is affected
| Product | Vulnerable | Fixed |
|---|---|---|
| Splunk Enterprise 10.6 | 10.6.0.5 | 10.6.1 |
| Splunk Enterprise 10.4 | 10.4.0–10.4.4 | 10.4.5 |
| Splunk Enterprise 10.2 | 10.2.0–10.2.8 | 10.2.9 |
| Splunk Enterprise 10.0 | 10.0.0–10.0.11 | 10.0.12 |
| Splunk Enterprise 9.4 | 9.4.0–9.4.16 | 9.4.17 |
| Enterprise Security, App for PCI Compliance | below 8.7.0 | 8.7.0 |
| Splunk SOAR | below 8.8.0 | 8.8.0 |
For some CVEs, the advisory text gives a lower version boundary than the table (for example 10.4.4 instead of 10.4.5). Go by the table – it is the stricter one. Splunk Cloud Platform does not appear in the Enterprise advisory's table.
How to tell if you were compromised
Splunk has not published indicators of compromise or detections. Our suggestions (not vendor guidance):
- Check whether
pass4SymmKeyis empty or default:splunk btool server list --debug | grep -i pass4SymmKey(the value is encrypted; a blank line is a warning sign). - In
_internaland_audit, look for calls to the clustering and RapidDiag REST endpoints from unknown IP addresses and unexpectedserver.confchanges. - Look for searches run under users who did not run them, and for new metric alerts or shared dashboards created by low-privileged accounts.
What to do
- Set a strong, unique
pass4SymmKeynow (at least 12 characters) inserver.confon every node, including the[clustering]stanza on standalone instances, then restart. This covers CVE-2026-76535, -76536 and -131192. - Upgrade Splunk Enterprise to 10.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17. Splunk lists no other mitigation for the SPL injection flaws.
- Upgrade Enterprise Security and the App for PCI Compliance to 8.7.0 and Splunk SOAR to 8.8.0. Until then, keep the ess_admin role and playbook permissions to the minimum.
- If you do not use RapidDiag, Splunk recommends disabling or removing the app (CVE-2026-131190); where possible, turn off Splunk Web (CVE-2026-131188).
- Do not expose the Splunk-to-Splunk receiving port (usually 9997) or the management interface (8089) to the internet.
Timeline
Update
- 19 Nov 2026: first version.
FAQ
I run a standalone Splunk with no cluster. Does the clustering flaw affect me?
Yes. According to Splunk, CVE-2026-76536 specifically affects standalone instances with clustering disabled that accept an empty clustering secret. The interim fix is a strong, unique pass4SymmKey (at least 12 characters) in the [clustering] stanza of server.conf, followed by a restart.
Does this affect Splunk Cloud?
The Splunk Enterprise advisory lists only Enterprise versions; Splunk Cloud Platform does not appear in its affected-versions table. Splunk manages Cloud itself. If you run Enterprise Security or other apps on-premises, patching them is up to you.
Why are there so many SPL injection bugs?
Most of the high-severity Enterprise flaws are injection of Splunk's own search language, SPL, via the REST API, metric alerts, shared dashboards and data model acceleration. A low-privileged user can run searches with higher privileges or read stored credentials. Some require the victim to open a crafted link or dashboard.
Sources
- Splunk – SVD-2026-1103: Security Vulnerabilities in Splunk Enterprise – November 2026 (18 Nov 2026)
- Splunk – SVD-2026-1106: Security Vulnerabilities in Splunk Enterprise Security – November 2026 (18 Nov 2026)
- Splunk – SVD-2026-1108: Security Vulnerabilities in Splunk SOAR – November 2026 (18 Nov 2026)
- Splunk – security advisories index
Spotted a mistake? Let us know and we will correct it openly.