CVE-2025-58782

There is a serialization of Untrusted Data vulnerability in Apache Jackrabbit Core and Apache Jackrabbit JCR Commons.

This issue affects Apache Jackrabbit Core: from 1.0.0 through 2.22.1; Apache Jackrabbit JCR Commons: from 1.0.0 through 2.22.1.

Deployments that accept JNDI URIs for JCR lookup from untrusted users allows them to inject malicious JNDI references, potentially leading to arbitrary code execution through deserialization of untrusted data. Users are recommended to upgrade to version 2.22.2. JCR lookup through JNDI has been disabled by default in 2.22.2. Users of this feature need to enable it explicitly and are adviced to review their use of JNDI URI for JCR lookup.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2025-58782 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.22.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-58782? CVE-2025-58782 is a medium-severity insecure deserialization vulnerability in org.apache.jackrabbit:jackrabbit-core (maven), affecting versions >= 1.0.0, < 2.22.2. It is fixed in 2.22.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2025-58782? CVE-2025-58782 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-58782?
   • org.apache.jackrabbit:jackrabbit-core (maven) (versions >= 1.0.0, < 2.22.2)
   • org.apache.jackrabbit:jackrabbit-jcr-commons (maven) (versions >= 1.0.0, < 2.22.2)
4. Is there a fix for CVE-2025-58782? Yes. CVE-2025-58782 is fixed in 2.22.2. Upgrade to this version or later.
5. Is CVE-2025-58782 exploitable, and should I be worried? Whether CVE-2025-58782 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-58782 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-58782?
   • Upgrade org.apache.jackrabbit:jackrabbit-core to 2.22.2 or later
   • Upgrade org.apache.jackrabbit:jackrabbit-jcr-commons to 2.22.2 or later