Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-76536Authentication Bypass through the Cluster Configuration REST API in Splunk Enterprise

Description

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could use an empty clustering shared secret to read and modify clustering configuration through the cluster configuration Representational State Transfer (REST) API endpoint on a standalone instance. This could expose clustering configuration, persist attacker-controlled clustering settings, and disrupt clustering operations. The vulnerability is possible because Splunk Enterprise accepts the empty clustering shared secret as a shared-authentication candidate on a standalone instance when clustering is turned off.

Timeline

  1. ID reserved

    By cisco

  2. · 3 months later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-76536, by who scored it
Scored byCVSSScoreVector
ciscoCNA (assigner)3.1Critical9.4CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
NVDNVD · Received3.1Critical9.4CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
EPSS (exploitation in 30 days)
Not scored

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.4.

Affected products

  • Splunk · Splunk Enterprise

    • affected 10.4 – < 10.4.5
    • affected 10.2 – < 10.2.9
    • affected 10.0 – < 10.0.12
    • affected 9.4 – < 9.4.17

What to do

Solution: Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.

Workaround: If you cannot immediately upgrade to a fixed version, set a strong, unique `pass4SymmKey` value in the `[clustering]` stanza in the `server.conf` configuration file, including on standalone instances. The `pass4SymmKey` value must contain at least 12 characters. The file is at `etc/system/local/server.conf` under the Splunk Enterprise installation directory. Restart Splunk Enterprise for the change to take effect. For more information see [Secure Splunk Enterprise services with pass4SymmKey](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/secure-distributed-and-clustered-splunk-environments/secure-splunk-enterprise-services-with-pass4symmkey) in the Splunk documentation.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-76536 badge
[![CVE-2026-76536](https://cveledger.app/badge/CVE-2026-76536.svg)](https://cveledger.app/cve/CVE-2026-76536)

Record last updated .