Splunk Enterprise EUVD-2026-36088

Exploitation requires only network reachability to the PostgreSQL sidecar service endpoint shipped with Splunk Enterprise and Splunk Cloud Platform - no credentials, no user interaction, and no non-default configuration are needed per the description, since the missing authentication is in the sidecar itself rather than gated behind an optional feature. The realistic limiting factor is network exposure of the sidecar port: in typical Splunk deployments this service is not intended to be reachable from arbitrary networks, so external exploitability depends on whether the operator has placed the sidecar port behind a firewall or bound it to non-public interfaces, while internal attackers and any deployment that inadvertently exposes the port are exploitable without further preconditions.

All available signals point in the same direction: the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H scores 9.8 because exploitation is network-reachable, low-complexity, requires no privileges or user interaction, and yields full CIA impact - consistent with a missing-auth file-write primitive that can be chained into RCE on a Splunk indexer or search head. EPSS, KEV status, and SSVC decision values were not provided in the input, so probabilistic exploitation likelihood and CISA-confirmed in-the-wild use cannot be asserted; no public exploit identified at time of analysis. The conflicting signal worth flagging is exposure scope: the description says 'network-reachable user', but in practice the PostgreSQL sidecar port is typically bound to localhost or the internal cluster network - defenders should verify whether their deployment exposes the sidecar port externally before treating this as an internet-facing 9.8, while still patching urgently because internal-network exploitation by a foothold attacker is fully sufficient for impact.

An attacker with network reach to a Splunk indexer or search head - either from the internet (if exposed) or after gaining an initial foothold on the internal network - sends a crafted unauthenticated request to the PostgreSQL sidecar endpoint and instructs it to truncate or create a file at an attacker-chosen path. By targeting files such as Splunk configuration, authentication state, or a writable script path used by a scheduled task, the attacker escalates the file-write primitive into denial of service, configuration tampering, or code execution under the Splunk service account. No public exploit identified at time of analysis, but the CVSS AV:N/AC:L/PR:N/UI:N profile means weaponization once the endpoint and request format are reverse-engineered from the patch is straightforward.