Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2025-53689

HIGH

Apache Jackrabbit vulnerable to blind XXE attack due to insecure document build

Also known asGHSA-44c3-38h8-9fh9
Published
Jul 14, 2025
Updated
Apr 10, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk37th percentile+0.25%
0.00%0.32%0.64%0.97%0.1%0.5%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected
org.apache.jackrabbit:jackrabbit-spi-commonsorg.apache.jackrabbit:jackrabbit-spi-commonsorg.apache.jackrabbit:jackrabbit-spi-commonsorg.apache.jackrabbit:jackrabbit-coreorg.apache.jackrabbit:jackrabbit-coreorg.apache.jackrabbit:jackrabbit-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Blind XXE Vulnerabilities in jackrabbit-spi-commons and jackrabbit-core in Apache Jackrabbit < 2.23.2 due to usage of an unsecured document build to load privileges.

Users are recommended to upgrade to versions 2.20.17 (Java 8), 2.22.1 (Java 11) or 2.23.2 (Java 11, beta versions), which fix this issue. Earlier versions (up to 2.20.16) are not supported anymore, thus users should update to the respective supported version.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.jackrabbit:jackrabbit-spi-commons2.20.0&&< 2.20.172.20.17
Mavenorg.apache.jackrabbit:jackrabbit-spi-commons2.22.0&&< 2.22.12.22.1
Mavenorg.apache.jackrabbit:jackrabbit-spi-commons2.23.0-beta&&< 2.23.2-beta2.23.2-beta
Mavenorg.apache.jackrabbit:jackrabbit-core2.23.0-beta&&< 2.23.2-beta2.23.2-beta
Mavenorg.apache.jackrabbit:jackrabbit-core2.20.0&&< 2.20.172.20.17
Mavenorg.apache.jackrabbit:jackrabbit-core2.22.0&&< 2.22.12.22.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.jackrabbit:jackrabbit-spi-commons. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.apache.jackrabbit:jackrabbit-spi-commons to 2.20.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-53689 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2025-53689 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-53689. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Blind XXE Vulnerabilities in jackrabbit-spi-commons and jackrabbit-core in Apache Jackrabbit < 2.23.2 due to usage of an unsecured document build to load privileges. Users are recommended to upgrade to versions 2.20.17 (Java 8), 2.22.1 (Java 11) or 2.23.2 (Java 11, beta versions), which fix this issue. Earlier versions (up to 2.20.16) are not supported anymore, thus users should update to the respective supported version.
O3 Security · Impact-Aware SCA

Is CVE-2025-53689 in your dependencies?

O3 detects CVE-2025-53689 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.