Thanks a lot Tilman. I can confirm that issue is caused by dependency mismatch with Apache Commons Compress. In our case the dependency was coming from io.github.bonigarcia:webdrivermanager which is still using version 1.27.1 instead of latest 1.28.0. I have added an exclusion and now things are working fine.
Thanks and regards, Sandeep Kulkarni From: Tilman Hausherr <thaush...@t-online.de> Sent: Wednesday, September 10, 2025 4:17 PM To: user@tika.apache.org Subject: Re: Tika 3.2.2 parsing issue Hi, Make sure you have the latest commons compress in the class path, most likely you have a bad dependency https://issues.apache.org/jira/browse/TIKA-4469 (contains code to check what version you are using) Tilman Am 10.09.2025 um 11:45 schrieb Sandeep Kulkarni via user: Hello All, We are using Tika as library within a Java application. We are currently using Tika 3.2.1 and want to upgrade to 3.2.2 for getting fix for CVE-2025-54988. However, after upgrading we are observing an issue with parsing for all the files. The stack trace is like below: Caused by: org.apache.commons.compress.archivers.ArchiveException: No Archiver found for the stream signature at org.apache.commons.compress.archivers.ArchiveStreamFactory.detect(ArchiveStreamFactory.java:295) at org.apache.tika.detect.zip.DefaultZipContainerDetector.detectArchiveFormat(DefaultZipContainerDetector.java:122) at org.apache.tika.detect.zip.DefaultZipContainerDetector.detect(DefaultZipContainerDetector.java:180) at org.apache.tika.detect.CompositeDetector.detect(CompositeDetector.java:84) at org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:179) at org.apache.tika.parser.ParsingReader$ParsingTask.run(ParsingReader.java:268) ... 4 common frames omitted Few details which will be useful for understanding our use of Tika. 1. We are importing tika-core and tika-parsers-standard-package into our application. 2. We use AutoDetectParser for auto detecting file type and parse it. We also make use of ParsingReader so that we can control the thread pool to be used for extraction. 3. We use TikaInputStream to generate stream before calling parse method of ParsingReader. Can you please guide me what could the reason for above errors? I don’t find any details about any changes done in 3.2.2 release notes which can cause this issue. Thanks and regards, Sandeep Kulkarni