Skip to content
VulniPulse
Advisory severityHigh8.8Splunk

High [CVE-2026-76298] Use of Hard-coded Cryptographic Key in the PostgreSQL Sidecar Service in Splunk Enterprise

This high-severity Splunk advisory covers CVE-2026-76298 affecting Splunk Enterprise.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-76298 Source published Source updated

VulniPulse record published

CVE-2026-76298
Affected products & platforms
SplunkSplunk Enterprise
Open source advisory

Android app · Google Play

Monitor future Splunk CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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 ( ), server.conf ( ), and Sidecar configuration settings ( ) in the Splunk documentation.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.4
  • Splunk Enterprise 10.2 before 10.2.8

Official advisory · high-confidence parse· fetched 6 hours ago·verify at source

Fixed versions
  • 10.4.4
  • 10.2.8

Official advisory · high-confidence parse· fetched 6 hours ago·verify at source

Mitigation

Upgrade to a fixed release: 10.4.4, 10.2.8. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 6 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.