# Apache Jackrabbit vulnerable to blind XXE attack due to insecure document build Advisory record · `GHSA-44c3-38h8-9fh9` - **Identifiers:** `GHSA-44c3-38h8-9fh9` · `CVE-2025-53689` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** No - **Weakness (CWE):** [CWE-611](https://cwe.mitre.org/data/definitions/611.html) - **Tags:** [XML external entities (XXE)](https://agentprime.io/advisories/tag/xxe.md) - **Published:** 14 Jul 2025 - **Updated:** 5 Nov 2025 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 14 Jul 2025, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.apache.jackrabbit:jackrabbit-spi-commons` (Maven): affected `>=2.20.0, <2.20.17 || >=2.22.0, <2.22.1 || >=2.23.0-beta, <2.23.2-beta`; fixed in `2.20.17`, `2.22.1`, `2.23.2-beta` - `org.apache.jackrabbit:jackrabbit-core` (Maven): affected `>=2.23.0-beta, <2.23.2-beta || >=2.20.0, <2.20.17 || >=2.22.0, <2.22.1`; fixed in `2.23.2-beta`, `2.20.17`, `2.22.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Jackrabbit packages jackrabbit-spi-commons and jackrabbit-core are affected by a blind XXE (XML external entity) vulnerability in versions 2.20.0 to before 2.20.17, 2.22.0 to before 2.22.1, and 2.23.0-beta to before 2.23.2-beta, caused by an insecure document build used to load privileges. The source does not describe what an attacker must have or how it is triggered, though the blind XXE class implies a crafted XML input is processed. Upgrade jackrabbit-spi-commons and jackrabbit-core to 2.20.17, 2.22.1, or 2.23.2-beta, depending on the branch in use. 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 - 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.0054, the 45th percentile, on 8 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-44c3-38h8-9fh9) ## Sources - [GitHub Advisory Database: GHSA-44c3-38h8-9fh9](https://github.com/advisories/GHSA-44c3-38h8-9fh9) - [OSV: GHSA-44c3-38h8-9fh9](https://osv.dev/vulnerability/GHSA-44c3-38h8-9fh9) - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .