CVE-2025-58782: Apache Jackrabbit · Core and JCR Commons are vulnerable to Deserialization of Untrusted Data
Affects org.apache.jackrabbit:jackrabbit-coreSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.22.2 when convenient.
Data as of 4 Nov 2026, 18:17 UTC
- Patch
- Available – fixed in 2.22.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade org.apache.jackrabbit:jackrabbit-core and org.apache.jackrabbit:jackrabbit-jcr-commons to 2.22.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavenorg.apache.jackrabbit:jackrabbit-core | Affected
| Fixed in
|
| Mavenorg.apache.jackrabbit:jackrabbit-jcr-commons | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected Apache Jackrabbit Core and JCR Commons installations to version 2.22.2 or later. This version disables JCR lookup through JNDI by default, mitigating the vulnerability. Users who require JNDI URI lookups must explicitly enable this feature and carefully review their usage to avoid exposure.
Description
Apache Jackrabbit Core and JCR Commons versions from 1.0.0 up to 2.22.1 are vulnerable to deserialization of untrusted data via JNDI URI lookups. This vulnerability allows attackers who can supply JNDI URIs to inject malicious references, potentially leading to arbitrary code execution. The issue is fixed in version 2.22.2, where JCR lookup through JNDI is disabled by default. Users relying on this feature must explicitly enable it and carefully review their usage.
References
- nvd.nist.gov/vuln/detail/CVE-2025-58782 (opens in a new tab)
- github.com/apache/jackrabbit/pull/229 (opens in a new tab)
- github.com/apache/jackrabbit (opens in a new tab)
- issues.apache.org/jira/browse/JCR-5135 (opens in a new tab)
- lists.apache.org/thread/t4wdrost6dh17dh406g792j9wq6xmy6v (opens in a new tab)
- openwall.com/lists/oss-security/2025/09/06/3 (opens in a new tab)