On this page (7 sections)

A critical authentication flaw, CVE-2026-76535, affects Splunk Enterprise. According to the GitHub Advisory Database entry, an unauthenticated user could run arbitrary Search Processing Language (SPL) searches through RapidDiag task collection, acting as an authenticated user. The cause is that Splunk Enterprise accepts an empty shared secret when authenticating those requests.

If you run Splunk Enterprise to collect logs, security events or operational data from your websites and servers, you should check your version now. The data stored in Splunk is often some of the most sensitive information an organization holds.

What happened

The vulnerability was published on November 19, 2026 through the National Vulnerability Database and the GitHub Advisory Database, with a reference to Splunk's own advisory, SVD-2026-1103. The description says that with this access, an attacker could read or modify data and configuration available to the authenticated user whose context the searches run in.

Only a single underlying description is available so far. The NVD record repeats the same text, so it is not independent confirmation. The GitHub entry is marked unreviewed and lists affected and patched versions as unknown in its package fields, so use Splunk's advisory as the authority for exact fix guidance.

Technical details

RapidDiag is a Splunk Enterprise feature whose task-collection requests are authenticated with a shared secret, a value both sides must know. The flaw is that the server accepts an empty secret as valid. In plain terms, the lock exists, but it opens when no key is presented.

This is a classic improper authentication problem (CWE-287): the product does not properly prove that the caller is who it claims to be. The CVSS v3.1 vector shown in the GitHub advisory is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, which translates to:

  • Network attack vector: reachable remotely, no local access needed.
  • Low complexity and no privileges or user interaction required.
  • High impact on confidentiality and integrity: data can be read or changed.
  • No availability impact rated.

Because the searches run as an authenticated user, the real-world impact depends on how privileged that user is. The sources do not say which account is used, so treat the worst case as plausible until Splunk's guidance says otherwise.

Who is affected

Any Splunk Enterprise instance on a version below the following thresholds is described as affected:

Affected Splunk Enterprise versions per release line (from the CVE description)
Release lineAffected versions
10.6Below 10.6.1
10.4Below 10.4.5
10.2Below 10.2.9
10.0Below 10.0.12
9.4Below 9.4.17

The sources do not say whether RapidDiag is enabled by default, which port or interface serves it, or what network exposure an attacker needs. Do not assume a deployment is safe because it is internal, and confirm the details in Splunk's advisory.

How to check your exposure

Start by finding every Splunk Enterprise instance you run and noting the version of each.

Show the installed Splunk Enterprise version (run on each Splunk host, from the Splunk bin…Shell
./splunk version

Compare the result with the table above. If your version is below the threshold for its release line, the instance is within the affected range.

The research does not describe indicators of compromise for this flaw. Absence of obvious signs does not prove an instance was not abused.

What to do now

  1. Inventory all Splunk Enterprise instances and record their versions.
  2. Read Splunk's advisory SVD-2026-1103 for the exact fixed builds, the affected interface and any workaround it lists.
  3. Upgrade each affected instance to a fixed version for its release line (10.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17, or later).
  4. As general hardening, limit network access to Splunk hosts so only trusted admin and cluster systems can reach them.
  5. Review recent search activity and configuration changes for anything you do not recognize, as general good practice.
  6. If you find suspicious activity, rotate credentials and tokens stored in or accessible through Splunk, and follow your incident process.
Caution. Upgrading Splunk usually means restarting services and, in clustered setups, a specific upgrade order. Plan a maintenance window and follow Splunk's upgrade documentation rather than patching nodes ad hoc.
The sources list no official workaround. Restricting network access is general hardening only: the research does not confirm which interface exposes RapidDiag, so it should not be relied on as a fix. Upgrading to a fixed version is the only remedy the sources support.

Detection and monitoring

The research gives no detection guidance specific to this flaw. As general good practice, review Splunk's audit and internal logs for searches run at unusual times or by accounts that should not be running them, and for changes to saved searches or configuration that you did not approve.

For outside-in visibility of what your public hosts expose, a read-only scan and change monitoring can help you spot services that should not be reachable, though they cannot tell you whether this specific flaw is present.

For related reading on authentication gaps in data and security platforms, see our article on the IBM Guardium S-TAP missing authentication flaw.

What is still unknown

  • Whether the flaw is being exploited in the wild: the sources reviewed do not say.
  • Public exploit code: none is mentioned, and the GitHub entry notes no known source code.
  • Exact fixed build numbers and any workaround: confirm these in Splunk's advisory, as the GitHub entry lists them as unknown.
  • Which authenticated account the searches run as, and which port or interface serves RapidDiag.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-76535 - GitHub Advisory Databasegithub.com
  2. CVE-2026-76535: In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could run arbitrary Search Processing Language (SPL)…nvd.nist.gov ·
  • Splunk
  • CVE-2026-76535
  • RapidDiag
  • Authentication
  • Patching