<?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: MONGODB vulnerability in ZLIB in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757494#M23744</link>
    <description>&lt;P&gt;If you have an active entitlement and raising support cases gives you error, call your local Splunk sales contact to escalate the issue.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jan 2026 11:26:27 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2026-01-20T11:26:27Z</dc:date>
    <item>
      <title>MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757424#M23726</link>
      <description>&lt;P&gt;Hello.&lt;BR /&gt;Recently a critical vulnerability was found in ZLIB of MongoDB.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories/vulnerability-in-mongodb-product-mongodb-server-leak" target="_blank"&gt;https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories/vulnerability-in-mongodb-product-mongodb-server-leak&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Is there a way resolve this internal issue?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 09:34:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757424#M23726</guid>
      <dc:creator>verbal_666</dc:creator>
      <dc:date>2026-01-19T09:34:51Z</dc:date>
    </item>
    <item>
      <title>Re: MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757427#M23727</link>
      <description>&lt;P&gt;It will probably be patched in some subsequent release. But the standard disclaimer for all alarm bell ringers applies - verify the scope and exposition surface of your "vulnerabilities". Even if there is an issue with mongodb, normally you shouldn't provide remote access (or even a local one - you don't normally allow users shell access to your Splunk components).&lt;/P&gt;&lt;P&gt;So don't just blindly rush to patch everything just because Nessus or Nexpose flagged something red.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 10:25:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757427#M23727</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2026-01-19T10:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757428#M23728</link>
      <description>&lt;P&gt;I know it, only SPLUNK instance can access mongodb from localhost only and our SPLUNK it's not exposed outside, only in Intranet.&lt;/P&gt;&lt;P&gt;But my Company wants a solution or a&amp;nbsp;valid explanation to exclude vulnerabilities on the instances&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":sad_but_relieved_face:"&gt;😥&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Maybe a formal official SPLUNK communication could help!&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 11:01:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757428#M23728</guid>
      <dc:creator>verbal_666</dc:creator>
      <dc:date>2026-01-19T11:01:26Z</dc:date>
    </item>
    <item>
      <title>Re: MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757429#M23729</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/28550"&gt;@verbal_666&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Keep an eye on&amp;nbsp;&lt;A href="https://advisory.splunk.com/" target="_blank"&gt;https://advisory.splunk.com/&lt;/A&gt;&amp;nbsp;for any updates regarding this Vuln which will contain details around if/how mitigations should be applied to Splunk.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are also due a maintenance update to 9.4.x imminently (10.2 was released last week).&lt;/P&gt;&lt;P&gt;Its also worth raising a support case with Splunk directly to discuss this as they may be able to provide additional information under your contract/NDA with them.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 11:12:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757429#M23729</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2026-01-19T11:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757432#M23731</link>
      <description>&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 11:17:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757432#M23731</guid>
      <dc:creator>verbal_666</dc:creator>
      <dc:date>2026-01-19T11:17:09Z</dc:date>
    </item>
    <item>
      <title>Re: MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757433#M23732</link>
      <description>&lt;P&gt;Yes. That's why good vulnerability management process includes actual risk management, not just pure CVSS or whatever magical number the scanner comes up with. The proper behaviour here - for me - would be to create an exception with an explanation of the vulnerability characteristics and "applicability"&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 11:50:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757433#M23732</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2026-01-19T11:50:25Z</dc:date>
    </item>
    <item>
      <title>Re: MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757492#M23742</link>
      <description>&lt;P&gt;Can someone, please, open a case to SPLUNK for official communication?&lt;BR /&gt;I get error after sending a NEW CASE&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="verbal_666_0-1768905186492.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/41220i4966D40FA814DAAB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="verbal_666_0-1768905186492.png" alt="verbal_666_0-1768905186492.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;MONGODB Vulnerability CVE-2025-14847

https://www.mongodb.com/company/blog/news/mongodb-server-security-update-december-2025

SPLUNK ENTERPRISE
9.3.X
9.4.X
10.X.X

/opt/splunk/bin/splunk cmd mongod -version

SECURITY ISSUE&lt;/LI-CODE&gt;</description>
      <pubDate>Tue, 20 Jan 2026 10:34:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757492#M23742</guid>
      <dc:creator>verbal_666</dc:creator>
      <dc:date>2026-01-20T10:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757494#M23744</link>
      <description>&lt;P&gt;If you have an active entitlement and raising support cases gives you error, call your local Splunk sales contact to escalate the issue.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 11:26:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757494#M23744</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2026-01-20T11:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: MONGODB vulnerability in ZLIB</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757943#M23803</link>
      <description>&lt;P&gt;&lt;A href="https://advisory.splunk.com/advisories/SVD-2026-0101" target="_blank"&gt;https://advisory.splunk.com/advisories/SVD-2026-0101&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 07:13:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/MONGODB-vulnerability-in-ZLIB/m-p/757943#M23803</guid>
      <dc:creator>verbal_666</dc:creator>
      <dc:date>2026-02-04T07:13:00Z</dc:date>
    </item>
  </channel>
</rss>

