{"api_version":"1","generated_at":"2026-10-22T02:31:51+00:00","cve":"CVE-2026-76298","urls":{"html":"https://cve.report/CVE-2026-76298","api":"https://cve.report/api/cve/CVE-2026-76298.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-76298","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-76298"},"summary":{"title":"Use of Hard-coded Cryptographic Key in the PostgreSQL Sidecar Service in Splunk Enterprise","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.\nThe 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.\nFor 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.","state":"PUBLISHED","assigner":"cisco","published_at":"2026-10-21 23:17:27","updated_at":"2026-10-21 23:17:27"},"problem_types":["CWE-321","CWE-321 The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered."],"metrics":[{"version":"3.1","source":"psirt@cisco.com","type":"Primary","score":"8.8","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"8.8","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":8.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://advisory.splunk.com/advisories/SVD-2026-1007","name":"https://advisory.splunk.com/advisories/SVD-2026-1007","refsource":"psirt@cisco.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-76298","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-76298","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Splunk","product":"Splunk Enterprise","version":"affected 10.4 10.4.4 custom","platforms":[]},{"source":"CNA","vendor":"Splunk","product":"Splunk Enterprise","version":"affected 10.2 10.2.8 custom","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade Splunk Enterprise to versions 10.4.4, 10.2.8, 10.0.11, and 9.4.16 or higher.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"If you cannot immediately upgrade to a fixed version, turn off the PostgreSQL sidecar service.\nAdd the following stanza in the `server.conf` configuration file: `[postgres]` `disabled = true`. Restart Splunk Enterprise for the change to take effect.\nDo not apply this workaround if you use Edge Processor, OpAmp, or SPL2 data pipelines on the instance. Turning off PostgreSQL breaks these features and can cascade to dependent sidecar processes. Core search, indexing, and dashboard functionality are not affected.\nFor more information see [Sidecar configuration settings](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/splunk-sidecars/sidecar-configuration-settings) in the Splunk documentation.","time":"","lang":"en"}],"exploits":[],"credits":[{"source":"CNA","value":"Ofir Alkoby, Security Researcher, a.security","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"modules":["splunkd"],"product":"Splunk Enterprise","vendor":"Splunk","versions":[{"lessThan":"10.4.4","status":"affected","version":"10.4","versionType":"custom"},{"lessThan":"10.2.8","status":"affected","version":"10.2","versionType":"custom"}]}],"credits":[{"lang":"en","type":"reporter","value":"Ofir Alkoby, Security Researcher, a.security"}],"datePublic":"2026-10-21T00:00:00.000Z","descriptions":[{"lang":"en","value":"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.\nThe 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.\nFor 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."}],"metrics":[{"cvssV3_1":{"baseScore":8.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-321","description":"The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.","lang":"en","type":"cwe"}]}],"providerMetadata":{"dateUpdated":"2026-10-21T22:52:00.185Z","orgId":"d1c1063e-7a18-46af-9102-31f8928bc633","shortName":"cisco"},"references":[{"url":"https://advisory.splunk.com/advisories/SVD-2026-1007"}],"solutions":[{"lang":"en","value":"Upgrade Splunk Enterprise to versions 10.4.4, 10.2.8, 10.0.11, and 9.4.16 or higher."}],"source":{"advisory":"SVD-2026-1007","discovery":""},"title":"Use of Hard-coded Cryptographic Key in the PostgreSQL Sidecar Service in Splunk Enterprise","workarounds":[{"lang":"en","value":"If you cannot immediately upgrade to a fixed version, turn off the PostgreSQL sidecar service.\nAdd the following stanza in the `server.conf` configuration file: `[postgres]` `disabled = true`. Restart Splunk Enterprise for the change to take effect.\nDo not apply this workaround if you use Edge Processor, OpAmp, or SPL2 data pipelines on the instance. Turning off PostgreSQL breaks these features and can cascade to dependent sidecar processes. Core search, indexing, and dashboard functionality are not affected.\nFor more information see [Sidecar configuration settings](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/splunk-sidecars/sidecar-configuration-settings) in the Splunk documentation."}]}},"cveMetadata":{"assignerOrgId":"d1c1063e-7a18-46af-9102-31f8928bc633","assignerShortName":"cisco","cveId":"CVE-2026-76298","datePublished":"2026-10-21T22:52:00.185Z","dateReserved":"2026-08-19T12:02:03.623Z","dateUpdated":"2026-10-21T22:52:00.185Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-21 23:17:27","lastModifiedDate":"2026-10-21 23:17:27","problem_types":["CWE-321","CWE-321 The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered."],"metrics":{"cvssMetricV31":[{"source":"psirt@cisco.com","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":2.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"76298","Ordinal":"1","Title":"Use of Hard-coded Cryptographic Key in the PostgreSQL Sidecar Se","CVE":"CVE-2026-76298","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"76298","Ordinal":"1","NoteData":"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.\nThe 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.\nFor 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.","Type":"Description","Title":"Use of Hard-coded Cryptographic Key in the PostgreSQL Sidecar Se"}]}}}