Potential Vulnerabilities Due To Hidden Dependencies

I am a student at Paderborn University and am analyzing security risks introduced by hidden dependencies in my master’s thesis. Software security researchers and I have found that this GitHub project incorporates known vulnerabilities within modified dependencies.

What are Hidden Dependencies?
Dependency modifications such as re-bundling and re-packaging (introduced for example by the Maven Shade plugin) can hide the inclusion of potentially vulnerable dependencies, as those dependencies are not found by vulnerability scanners that rely on metadata. In our approach, we identified hidden dependencies by matching fingerprints of known-to-be-vulnerable dependencies to the JAR files of direct and transitive dependencies listed in the software bill of materials.

Suggested Solution
You can find a list of hidden vulnerable dependencies that are included in this project at the end of this message. Please note that exploitability has not been investigated. We recommend either removing the affected dependencies or updating them to newer versions.

Your Perspective
As part of my master’s thesis, I am investigating awareness and patching behavior related to such hidden vulnerable dependencies. I would appreciate it if you could share your perspective and take a 5-minute anonymous survey at: https://umfragen.uni-paderborn.de/index.php/542735. Thank you!

List of vulnerable modified dependencies:

org.apache.tomcat.embed:tomcat-embed-core:9.0.64 includes:

• org.apache.tomcat:tomcat-catalina:9.0.64 - CVE-2023-28708, CVE-2024-52316, CVE-2025-55668
• org.apache.tomcat:tomcat-util:9.0.64 - CVE-2024-38286, CVE-2025-52434
• org.apache.tomcat:tomcat-util:9.0.64 - CVE-2024-38286, CVE-2025-52434

org.liquibase:liquibase-core:4.9.1 includes:

• org.apache.commons:commons-lang3:3.12.0 - CVE-2025-48924
• org.apache.commons:commons-text:1.9 - CVE-2022-42889

No files or tests are named. Start by locating the Maven declarations for org.apache.tomcat.embed:tomcat-embed-core and org.liquibase:liquibase-core, then inspect the resolved dependency tree for the listed vulnerable components. Done means removing or updating affected dependencies and verifying that the vulnerable versions are no longer included.