What I received from Splunk support: I would like to inform you that an estimated release date for the version that will fix the vulnerability for version 9.4.7,9.2.11 versions will be released by the end of December and for the 9.3.9,10.0.3 versions, we have an estimated time of arrival (ETA) of the end of March 2026.
... View more
Here is the best answer: To resolve the issue, please log in to Splunk and reload the deploy server: $ /opt/splunk/bin/splunk login Splunk username: admin # (use your actual username) Password: $ /opt/splunk/bin/splunk reload deploy-server -class XYZ This will reload the specified server class(es).
... View more
Here is the best answer: To resolve the issue, please log in to Splunk and reload the deploy server: $ /opt/splunk/bin/splunk login Splunk username: admin # (use your actual username) Password: $ /opt/splunk/bin/splunk reload deploy-server -class XYZ This will reload the specified server class(es).
... View more
Here is the best answer: To resolve the issue, please log in to Splunk and reload the deploy server: $ /opt/splunk/bin/splunk login Splunk username: admin # (use your actual username) Password: $ /opt/splunk/bin/splunk reload deploy-server -class XYZ This will reload the specified server class(es).
... View more
For your information: To resolve the issue, please log in to Splunk and reload the deploy server: $ /opt/splunk/bin/splunk login Splunk username: admin # (use your actual username) Password: $ /opt/splunk/bin/splunk reload deploy-server -class XYZ This will reload the specified server class(es).
... View more