Security alerts · November 19, 2026

Splunk Enterprise: two critical flaws let attackers bypass login and alter data and configuration

On November 18, 2026, Splunk fixed two critical flaws in Splunk Enterprise (CVSS 9.1 and 9.4). Splunk accepts an empty shared secret, so an attacker without a login can run searches or, on a standalone instance, change cluster settings. Update as soon as possible.

What happened

Splunk Enterprise is a platform for collecting and searching logs and machine data. Companies use it for monitoring, troubleshooting and as the backbone of security monitoring (SIEM).

On November 18, 2026, Splunk published security advisory SVD-2026-1103, which covers 38 vulnerabilities in total. The vendor rates two of them as critical: CVE-2026-76535 and CVE-2026-76536. They were added to the NVD database on November 19, 2026.

In both cases, Splunk accepts an empty shared secret as valid. CVE-2026-76535 affects the RapidDiag diagnostic tool and lets an attacker run searches without logging in. CVE-2026-76536 affects the cluster configuration interface. On a standalone instance with clustering turned off, it lets an attacker read and change cluster settings.

No exploitation is known so far. The flaws are not in the CISA KEV catalog, the European EUVD database records no exploitation, and the vendor does not mention any attacks.

Why it is dangerous

This is an authentication bypass (CWE-287). Picture a staff entrance with a keypad lock that opens even when you type nothing. Parts of Splunk that verify requests with a shared password accept an empty one, so anyone who can reach them over the network can use them.

The attacker needs no login and no user interaction, and the attack works over the network. With CVE-2026-76535, the vendor says an attacker could run arbitrary SPL searches as an authenticated user and read or modify the data and configuration that user can access. With CVE-2026-76536, on a standalone instance with clustering turned off, an attacker could read and persistently change cluster settings and disrupt clustering.

Splunk often holds sensitive logs from the whole company: logins, network traffic, application errors. Leaking or altering that data can help an attacker move further and cover their tracks.

CVSS is a severity scale from 0 to 10. Both flaws were scored by Cisco PSIRT (Splunk is owned by Cisco) using CVSS 3.1: CVE-2026-76535 scores 9.1 and CVE-2026-76536 scores 9.4, which is critical. The CISA KEV catalog lists flaws known to be exploited. These two are not in it yet. No EPSS score (probability of exploitation in the next 30 days) is available for them yet.

Who is affected

Splunk Enterprise is affected in these versions:

  • 10.6 branch before 10.6.1 (CVE-2026-76535 only)
  • 10.4.0 to 10.4.4
  • 10.2.0 to 10.2.8
  • 10.0.0 to 10.0.11
  • 9.4.0 to 9.4.16

Splunk Enterprise usually runs on company servers or in a private cloud as the central log store, often operated by IT or security teams. The risk is highest where the REST management interface (the splunkd service) is reachable from the internet or from large parts of the internal network.

According to the vendor, CVE-2026-76536 affects standalone instances with clustering turned off. The advisory covers Splunk Enterprise. If you use Splunk Cloud, these records do not state the impact, so check with Splunk.

How to check if you are affected

The quickest way to see the version is in the Splunk web interface under Help > About. On the server you can use these read-only commands that change nothing. If the SPLUNK_HOME variable is not set, they fall back to the default path /opt/splunk:

${SPLUNK_HOME:-/opt/splunk}/bin/splunk version
cat ${SPLUNK_HOME:-/opt/splunk}/etc/splunk.version

On a Windows server, run this in the command prompt:

"C:\Program Files\Splunk\bin\splunk.exe" version

Also check which addresses the splunkd service listens on and whether its port is reachable from outside. On Linux the command below helps (it shows process names only with root rights). Then compare the result with your firewall rules.

sudo ss -tlnp | grep splunkd

How to fix it

The vendor recommends upgrading Splunk Enterprise to 10.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17, or later, depending on the branch you run. These versions fix both critical flaws and other issues in advisory SVD-2026-1103.

Recommended steps:

  • First, use your firewall to limit access to the splunkd management interface to the addresses that really need it, especially if it is reachable from the internet.
  • Back up the configuration in $SPLUNK_HOME/etc.
  • Read the release notes for the target version.
  • Upgrade the most exposed servers first, then the rest.
  • In a distributed deployment, follow the component upgrade order in Splunk’s documentation.
  • After upgrading, confirm the version with splunk version and check that data ingestion works.

If you cannot upgrade right away, check advisory SVD-2026-1103 on advisory.splunk.com for any workarounds for your version. Restricting network access only buys time and does not replace the fix.

What if you may already be compromised

The vendor has not published specific indicators of compromise for these flaws. If the splunkd interface was reachable from an untrusted network, it is worth checking:

  • the splunkd_access.log file and the _internal index: requests to the RapidDiag and cluster configuration interfaces from unknown addresses
  • the _audit index: searches none of your staff ran
  • unexpected changes to cluster settings and modified or new saved searches
  • new or modified user accounts and roles

If you find suspicious activity, disconnect the server, preserve the logs and bring in an incident response specialist. Because Splunk collects logs from other systems, review those too and rotate passwords and tokens stored in Splunk.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.