<?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: CVE-2025-54988 &amp;amp; CVE-2025-66516 - Apache Tika Components' Vulverability. in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291265#M38202</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/45385"&gt;@eertul&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;One of my colleagues faced the same issue in his monitoring project and fixed it by upgrading the Tika components to the higher recommended versions in a lower environment first. After replacing the JARs under /opt/dynatrace-binary/elasticsearch/modules/ingest-attachment/ and restarting the service, the vulnerability scan cleared.&lt;BR /&gt;The recommended versions are:&lt;/P&gt;&lt;P&gt;tika-core → 3.2.2 or later&lt;BR /&gt;tika-parser-pdf-module → 3.2.2 or later&lt;BR /&gt;tika-parsers → 2.0.0 or later&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sujit&lt;/P&gt;</description>
    <pubDate>Wed, 10 Dec 2025 21:56:23 GMT</pubDate>
    <dc:creator>sujit_k_singh</dc:creator>
    <dc:date>2025-12-10T21:56:23Z</dc:date>
    <item>
      <title>CVE-2025-54988 &amp; CVE-2025-66516 - Apache Tika Components' Vulverability.</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291193#M38186</link>
      <description>&lt;P&gt;We found a lot of tika components under "/opt/dynatrace-binary/elasticsearch/modules/ingest-attachment/" which are affected from&amp;nbsp;CVE-2025-66516.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our version is 1.312. Is there any mitigation or suggestions?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 07:26:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291193#M38186</guid>
      <dc:creator>eertul</dc:creator>
      <dc:date>2025-12-10T07:26:24Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2025-54988 &amp; CVE-2025-66516 - Apache Tika Components' Vulverability.</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291194#M38187</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;If you read &lt;A title="this" href="https://www.cve.org/CVERecord?id=CVE-2025-54988" target="_blank" rel="noopener"&gt;this&lt;/A&gt;, they recommend to upgrade to version 3.2.2.&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 07:49:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291194#M38187</guid>
      <dc:creator>AntonPineiro</dc:creator>
      <dc:date>2025-12-10T07:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2025-54988 &amp; CVE-2025-66516 - Apache Tika Components' Vulverability.</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291219#M38194</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/45385"&gt;@eertul&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;In this article you'll have all the needed information on how to report a security vulnerability to the Dynatrace:&lt;BR /&gt;&lt;A href="https://community.dynatrace.com/t5/Troubleshooting/Report-a-security-vulnerability/ta-p/195675" target="_self"&gt;Report a security vulnerability&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;If you'll follow all the step from it, you'll get all your questions answered in the support ticket.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;As for the both CVE's you've mentioned, I can see already two internal tickets about them. As soon as there will be official communication about them available, you'll be able to see it in this article:&lt;BR /&gt;&lt;A href="https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Dynatrace-CVE-status-Common-Vulnerabilities-and-Exposures/ta-p/214793" target="_self"&gt;Dynatrace CVE status (Common Vulnerabilities and Exposures)&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 09:43:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291219#M38194</guid>
      <dc:creator>MaciejNeumann</dc:creator>
      <dc:date>2025-12-10T09:43:12Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2025-54988 &amp; CVE-2025-66516 - Apache Tika Components' Vulverability.</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291265#M38202</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/45385"&gt;@eertul&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;One of my colleagues faced the same issue in his monitoring project and fixed it by upgrading the Tika components to the higher recommended versions in a lower environment first. After replacing the JARs under /opt/dynatrace-binary/elasticsearch/modules/ingest-attachment/ and restarting the service, the vulnerability scan cleared.&lt;BR /&gt;The recommended versions are:&lt;/P&gt;&lt;P&gt;tika-core → 3.2.2 or later&lt;BR /&gt;tika-parser-pdf-module → 3.2.2 or later&lt;BR /&gt;tika-parsers → 2.0.0 or later&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sujit&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 21:56:23 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/CVE-2025-54988-amp-CVE-2025-66516-Apache-Tika-Components/m-p/291265#M38202</guid>
      <dc:creator>sujit_k_singh</dc:creator>
      <dc:date>2025-12-10T21:56:23Z</dc:date>
    </item>
  </channel>
</rss>

