Live › vulnerability › CVE-2026-76298
Go to dashboardA user without the admin or power Splunk roles can derive the PostgreSQL sidecar database superuser password from the search head cluster identifier shown in search job logs. That password lets them run arbitrary operating system commands as the account running Splunk Enterprise on search head cluster members.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
10.4.4 and 10.2.8; versions below these are affectedUpgrade Splunk Enterprise to 10.4.4 or 10.2.8 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In Splunk Enterprise versions below 10.4.4 and 10.2.8, a user who does not hold the "admin" or "power" Splunk roles could derive the PostgreSQL sidecar database superuser password and run arbitrary operating system commands as the user account running Splunk Enterprise on search head cluster members. The vulnerability is possible because the PostgreSQL sidecar service derives a privileged database password from the search head cluster identifier that appears in search job logs. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access), server.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/configuration-file-reference/10.2.0-configuration-file-reference/server.conf), and Sidecar configuration settings (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/splunk-sidecars/sidecar-configuration-settings) in the Splunk documentation.
This page as .md · .json · in your agent: get_signal("CVE-2026-76298")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.