CVE-2025-53689: Apache Jackrabbit vulnerable to blind XXE attack due to insecure document build

Quick answers

Is CVE-2025-53689 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-53689 being exploited in the wild.

How severe is CVE-2025-53689?

Low severity, with a CVSS score of 3.1, published 14 July 2025.

Which products and versions are affected?

org.apache.jackrabbit:jackrabbit-core (Maven) ECOSYSTEM:introduced=2.23.0-beta,fixed=2.23.2-beta; org.apache.jackrabbit:jackrabbit-spi-commons (Maven) ECOSYSTEM:introduced=2.20.0,fixed=2.20.17.

Is there a fix for CVE-2025-53689?

Yes. org.apache.jackrabbit:jackrabbit-core (Maven): upgrade to 2.23.2-beta or later; org.apache.jackrabbit:jackrabbit-spi-commons (Maven): upgrade to 2.20.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2025-53689?

Check whether you run org.apache.jackrabbit:jackrabbit-core (Maven) or org.apache.jackrabbit:jackrabbit-spi-commons (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• org.apache.jackrabbit:jackrabbit-core (Maven): upgrade to 2.23.2-beta or later

  # set org.apache.jackrabbit:jackrabbit-core to 2.23.2-beta in your pom.xml or build.gradle

• org.apache.jackrabbit:jackrabbit-spi-commons (Maven): upgrade to 2.20.17 or later

  # set org.apache.jackrabbit:jackrabbit-spi-commons to 2.20.17 in your pom.xml or build.gradle

Affected products

• org.apache.jackrabbit:jackrabbit-core (Maven) ECOSYSTEM:introduced=2.23.0-beta,fixed=2.23.2-beta
• org.apache.jackrabbit:jackrabbit-spi-commons (Maven) ECOSYSTEM:introduced=2.20.0,fixed=2.20.17

Identifiers

• CVE-2025-53689
• GHSA-44c3-38h8-9fh9