<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: postgres update in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760152#M24120</link>
    <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/316625"&gt;@SiddhatNegi&lt;/a&gt;&amp;nbsp; As per your screenshot, the vulnerability is related to PostgreSQL which Splunk bundles as part of its internal services. To remediate the vulnerability, upgrade Splunk Enterprise version to the latest maintenance release that includes PostgreSQL 17.8. Please do not attempt to patch PostgreSQL separately as it's part of Splunk bundle and can cause issues. You can review the Splunk advisory and search for the respective CVE number. If you can share the CVE details and Splunk version you are running, we can assist further to locate the actual version to fix it.&lt;BR /&gt;&lt;BR /&gt;Ref:&amp;nbsp;&lt;A href="https://advisory.splunk.com/" target="_blank" rel="noopener"&gt;Splunk Vulnerability Disclosure&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If this post addressed your question, you can:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Give it&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;karma&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;to show appreciation&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Mark it as the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;solution&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if it solved your issue&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":heavy_check_mark:"&gt;✔️&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Add a&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;comment&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if you’d like more details&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":pencil:"&gt;✏️&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;Acknowledging helpful answers keeps the community strong and motivates contributors to continue sharing their expertise.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Apr 2026 13:42:18 GMT</pubDate>
    <dc:creator>kknairr</dc:creator>
    <dc:date>2026-04-13T13:42:18Z</dc:date>
    <item>
      <title>postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760129#M24115</link>
      <description>&lt;P&gt;i am getting on vulnerability on one of the servers . how can i upgrade it.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SiddhatNegi_0-1776060583113.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/41921i26751261F6A131A8/image-size/medium?v=v2&amp;amp;px=400" role="button" title="SiddhatNegi_0-1776060583113.png" alt="SiddhatNegi_0-1776060583113.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Apr 2026 06:11:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760129#M24115</guid>
      <dc:creator>SiddhatNegi</dc:creator>
      <dc:date>2026-04-13T06:11:04Z</dc:date>
    </item>
    <item>
      <title>Re: postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760147#M24118</link>
      <description>&lt;P&gt;Check &lt;A href="https://advisory.splunk.com" target="_blank"&gt;https://advisory.splunk.com&lt;/A&gt;&amp;nbsp;and install the version of Splunk that fixes that vulnerability.&lt;/P&gt;&lt;P&gt;Do NOT attempt to patch postgres independently.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Apr 2026 11:56:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760147#M24118</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2026-04-13T11:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760152#M24120</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/316625"&gt;@SiddhatNegi&lt;/a&gt;&amp;nbsp; As per your screenshot, the vulnerability is related to PostgreSQL which Splunk bundles as part of its internal services. To remediate the vulnerability, upgrade Splunk Enterprise version to the latest maintenance release that includes PostgreSQL 17.8. Please do not attempt to patch PostgreSQL separately as it's part of Splunk bundle and can cause issues. You can review the Splunk advisory and search for the respective CVE number. If you can share the CVE details and Splunk version you are running, we can assist further to locate the actual version to fix it.&lt;BR /&gt;&lt;BR /&gt;Ref:&amp;nbsp;&lt;A href="https://advisory.splunk.com/" target="_blank" rel="noopener"&gt;Splunk Vulnerability Disclosure&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If this post addressed your question, you can:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Give it&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;karma&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;to show appreciation&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Mark it as the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;solution&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if it solved your issue&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":heavy_check_mark:"&gt;✔️&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Add a&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;comment&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if you’d like more details&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":pencil:"&gt;✏️&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;Acknowledging helpful answers keeps the community strong and motivates contributors to continue sharing their expertise.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Apr 2026 13:42:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760152#M24120</guid>
      <dc:creator>kknairr</dc:creator>
      <dc:date>2026-04-13T13:42:18Z</dc:date>
    </item>
    <item>
      <title>Re: postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760156#M24121</link>
      <description>&lt;P&gt;so splunk version is 10.2.0&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SiddhatNegi_0-1776088358053.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/41927i346AC7436AA552DA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="SiddhatNegi_0-1776088358053.png" alt="SiddhatNegi_0-1776088358053.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;hope this helps.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Apr 2026 13:52:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760156#M24121</guid>
      <dc:creator>SiddhatNegi</dc:creator>
      <dc:date>2026-04-13T13:52:53Z</dc:date>
    </item>
    <item>
      <title>Re: postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760176#M24122</link>
      <description>&lt;P&gt;What is wrong with addressing postgress directly?&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;tar xf postgresql-17.8.tar.bz2
      cd postgresql-17.8
      yum install -y gcc readline-devel zlib-devel libicu-devel perl-FindBin
      ./configure --prefix=/opt/splunk
      make
      make install&lt;/LI-CODE&gt;&lt;P&gt;this worked fine for me&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Apr 2026 14:06:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760176#M24122</guid>
      <dc:creator>nikhil14aug</dc:creator>
      <dc:date>2026-04-14T14:06:37Z</dc:date>
    </item>
    <item>
      <title>Re: postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760206#M24125</link>
      <description>&lt;P&gt;We don't know what customizations Splunk may have made to postgres.&amp;nbsp; Installing code from another source may introduce incompatibilities.&lt;/P&gt;&lt;P&gt;Code not released by Splunk may not be supported by Splunk.&lt;/P&gt;&lt;P&gt;Changing delivered files may trigger File Integrity Check warnings.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2026 12:01:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760206#M24125</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2026-04-15T12:01:28Z</dc:date>
    </item>
    <item>
      <title>Re: postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760627#M24204</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just upgraded to Splunk Enterprise 10.0.5 but I am still seeing the postgres vuln.&amp;nbsp; Do you know when postgres version 17.8 will be bundled with a new Splunk update?&lt;/P&gt;&lt;P&gt;Path : /opt/splunk/bin/postgres&lt;BR /&gt;Installed version : 17.7&lt;BR /&gt;Fixed version : 17.8&lt;/P&gt;&lt;P&gt;Third-Party Package Updates in Splunk Enterprise - April 2026&lt;/P&gt;&lt;P&gt;Package Remediation CVE Severity&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;protobuf&lt;EM&gt;1&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Upgraded protobuf to version 5.29.6&lt;/TD&gt;&lt;TD&gt;CVE-2026-0994&lt;/TD&gt;&lt;TD&gt;High&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;postgresql&lt;EM&gt;2&lt;/EM&gt;&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;&lt;STRONG&gt;Upgraded postgresql to version 17.7&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Multiple&lt;/TD&gt;&lt;TD&gt;Medium&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;azure-core&lt;EM&gt;3&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Upgraded azure-core to version 1.38.0&lt;/TD&gt;&lt;TD&gt;Multiple&lt;/TD&gt;&lt;TD&gt;High&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;OpenSSL&lt;EM&gt;4&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Upgraded OpenSSL to version 1.0.2zo&lt;/TD&gt;&lt;TD&gt;CVE-2026-22796&lt;/TD&gt;&lt;TD&gt;Low&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Fri, 01 May 2026 20:33:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760627#M24204</guid>
      <dc:creator>SplunkNinja</dc:creator>
      <dc:date>2026-05-01T20:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760628#M24205</link>
      <description>&lt;P&gt;Splunk 10.0.x is not the latest version.&amp;nbsp; Try 10.2.x.&lt;/P&gt;</description>
      <pubDate>Fri, 01 May 2026 21:00:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760628#M24205</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2026-05-01T21:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: postgres update</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760629#M24206</link>
      <description>&lt;P&gt;From what I can see in the latest&amp;nbsp;Third-Party Package Updates in Splunk Enterprise - April 2026&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;EM&gt;2&lt;/EM&gt; Upgraded &lt;STRONG&gt;postgresql&lt;/STRONG&gt; to version &lt;STRONG&gt;17.7&lt;/STRONG&gt; to remedy &lt;STRONG&gt;CVE-2025-12817&lt;/STRONG&gt; and &lt;STRONG&gt;CVE-2025-12818&lt;/STRONG&gt; in Splunk Enterprise versions &lt;STRONG&gt;10.2.2&lt;/STRONG&gt; and &lt;STRONG&gt;10.0.5&lt;/STRONG&gt;. Splunk Enterprise versions 9.4 and 9.3 are not affected&lt;/P&gt;&lt;P&gt;Seems like&amp;nbsp;Splunk Enterprise versions 10.2.2 and 10.0.5 mitigate &lt;STRONG&gt;CVE-2025-12817&lt;/STRONG&gt; and &lt;STRONG&gt;CVE-2025-12818&lt;/STRONG&gt;, but I am not seeing any mention of remediating&amp;nbsp;&lt;STRONG&gt;CVE-2026-2004&lt;/STRONG&gt;,&amp;nbsp;&lt;STRONG&gt;CVE-2026-2005&lt;/STRONG&gt;, and&amp;nbsp;&lt;STRONG&gt;CVE-2026-2006&lt;/STRONG&gt; in the latest &lt;STRONG&gt;Splunk Security Advisories&lt;/STRONG&gt;.&amp;nbsp; I need to wait before updating and see which Splunk version brings postgres to version &lt;STRONG&gt;17.8&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 May 2026 21:36:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/postgres-update/m-p/760629#M24206</guid>
      <dc:creator>SplunkNinja</dc:creator>
      <dc:date>2026-05-01T21:36:20Z</dc:date>
    </item>
  </channel>
</rss>

