# Apache Jackrabbit: Core and JCR Commons are vulnerable to Deserialization of Untrusted Data

Advisory record · `GHSA-cxvc-g8f2-4gmm`

- **Identifiers:** `GHSA-cxvc-g8f2-4gmm` · `CVE-2025-58782`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 8 Sept 2025
- **Updated:** 5 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Sept 2025, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.jackrabbit:jackrabbit-core` (Maven): affected `>=1.0.0, <2.22.2`; fixed in `2.22.2`
- `org.apache.jackrabbit:jackrabbit-jcr-commons` (Maven): affected `>=1.0.0, <2.22.2`; fixed in `2.22.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Jackrabbit Core and Apache Jackrabbit JCR Commons, versions 1.0.0 through 2.22.1, are vulnerable to deserialization of untrusted data. An attacker who can supply JNDI URIs for JCR lookup in a deployment could inject malicious JNDI references, potentially leading to arbitrary code execution. Upgrade both packages to version 2.22.2, where JCR lookup through JNDI is disabled by default; users who need this feature must enable it explicitly and should review their use of JNDI URIs for JCR lookup.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.014, the 72nd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-cxvc-g8f2-4gmm)

## Sources

- [GitHub Advisory Database: GHSA-cxvc-g8f2-4gmm](https://github.com/advisories/GHSA-cxvc-g8f2-4gmm)
- [OSV: GHSA-cxvc-g8f2-4gmm](https://osv.dev/vulnerability/GHSA-cxvc-g8f2-4gmm)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-58782>
- <https://github.com/apache/jackrabbit/pull/229>
- <https://github.com/apache/jackrabbit>
- <https://issues.apache.org/jira/browse/JCR-5135>
- <https://lists.apache.org/thread/t4wdrost6dh17dh406g792j9wq6xmy6v>
- <http://www.openwall.com/lists/oss-security/2025/09/06/3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cxvc-g8f2-4gmm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cxvc-g8f2-4gmm/>. Everything for agents: <https://agentprime.io/llms.txt>.