---
title: Tip: on every Splunk Enterprise node, including standalone ones, set a strong pass4SymmKey until you can upgrade, because the November auth bypasses rely on an empty shared secret | ctxsec
url: https://ctxsec.com/items/tip-splunk-set-a-non-empty-pass4symmkey-even-on-standalone-instances-until-you-upgrade
description: "CVE-2026-76536 works because a standalone Splunk instance with clustering off still accepts an empty clustering secret, and CVE-2026-76535 because RapidDiag accepts an empty shared secret. Splunk's workaround for 76536 is to set a strong, unique pass4SymmKey of at least 12 characters in the [clustering] stanza of etc/system/local/server.conf and restart. For RapidDiag, Splunk's guidance is to stop accepting empty-secret requests via pass4SymmKey, using the same value on every node in the service."
status: "official (Splunk SVD-2026-1103 mitigations)"
published: 2026-11-20
---

> CVE-2026-76536 works because a standalone Splunk instance with clustering off still accepts an empty clustering secret, and CVE-2026-76535 because RapidDiag accepts an empty shared secret. Splunk's workaround for 76536 is to set a strong, unique pass4SymmKey of at least 12 characters in the [clustering] stanza of etc/system/local/server.conf and restart. For RapidDiag, Splunk's guidance is to stop accepting empty-secret requests via pass4SymmKey, using the same value on every node in the service.

[← Tips & Guides](/tips) · [markdown](/items/tip-splunk-set-a-non-empty-pass4symmkey-even-on-standalone-instances-until-you-upgrade.md)

official (Splunk SVD-2026-1103 mitigations)

2026-11-20 7:44 PM ET

### Tip: on every Splunk Enterprise node, including standalone ones, set a strong pass4SymmKey until you can upgrade, because the November auth bypasses rely on an empty shared secret

- Audit: `splunk btool server list clustering --debug | grep pass4SymmKey` on each node.
- Restrict the management port (8089) to admin networks; it should never be internet-facing.
- Then upgrade to 10.6.1 / 10.4.5 / 10.2.9 / 10.0.12 / 9.4.17.

Sources: [Splunk SVD-2026-1103: Security Vulnerabilities in Splunk Enterprise - November 2026 (Nov 18, 2026)](https://advisory.splunk.com/advisories/SVD-2026-1103)
