Skip to content
Fencer Intel
high 8.8

CVE-2025-53689 json

Apache Jackrabbit: XXE vulnerability in jackrabbit-spi-commons

published last yr. modified 4mo ago also GHSA-44c3-38h8-9fh9 , EUVD-2025-21327

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.jackrabbit:jackrabbit-spi-commons 2.20.17, 2.22.1, 2.23.2-beta
  • maven org.apache.jackrabbit:jackrabbit-core 2.20.17, 2.22.1, 2.23.2-beta
  • Apache Software Foundation Apache Jackrabbit 2.20.17, 2.22.1, 2.23.2-beta
  • jackrabbit Debian 14, Debian 13 2.20.11-1.1

debian advisories DEBIAN-CVE-2025-53689

Is CVE-2025-53689 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-53689 updated cvss 7.1

jackrabbit-spi-commons: jackrabbit-core: Apache Jackrabbit XXE vulnerability

  • Red Hat Fuse 7 jackrabbit-core, jackrabbit-spi-commons
    affected: workaround, no fix planned “Will not fix”
  • Red Hat build of Apache Camel for Spring Boot 4 jackrabbit-core, jackrabbit-spi-commons
    not affected: inline mitigations already exist

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.jackrabbit:jackrabbit-spi-commons
>=2.20.0, <2.20.17
>=2.22.0, <2.22.1
>=2.23.0-beta, <2.23.2-beta
2.20.17
2.22.1
2.23.2-beta
maven org.apache.jackrabbit:jackrabbit-core
>=2.23.0-beta, <2.23.2-beta
>=2.20.0, <2.20.17
>=2.22.0, <2.22.1
2.23.2-beta
2.20.17
2.22.1

Affected products

  • Apache Software Foundation Apache Jackrabbit

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.