dbcve.org
JackrabbitApplication · Apache

CVE-2025-58782

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-08
Fix available
A fix is available. Upgrade to 2.22.2 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in Apache Jackrabbit Core and Apache Jackrabbit JCR Commons. This issue affects Apache Jackrabbit Core: from 1.0.0 through 2.22.1; Apache Jackrabbit JCR Commons: from 1.0.0 through 2.22.1. Deployments that accept JNDI URIs for JCR lookup from untrusted users allows them to inject malicious JNDI references, potentially leading to arbitrary code execution through deserialization of untrusted data. Users are recommended to upgrade to version 2.22.2. JCR lookup through JNDI has been disabled by default in 2.22.2. Users of this feature need to enable it explicitly and are adviced to review their use of JNDI URI for JCR lookup.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Jackrabbit Core and JCR Commons accept JNDI URIs for JCR lookup from untrusted users, allowing injection of malicious JNDI references that deserialize untrusted data and potentially achieve arbitrary code execution.

MitigationUpgrade to Apache Jackrabbit version 2.22.2 where JNDI-based JCR lookup is disabled by default, and explicitly review any remaining JNDI URI usage.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JackrabbitApplication
Affected:>= 1.0.0, < 2.22.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jackrabbit version
    Locate the jackrabbit-core JAR file in your application and check its version (typically in META-INF/MANIFEST.MF or filename). Also check pom.xml or build.gradle dependencies if present.
    Affected if The version is 2.22.2 or higher, the system is NOT affected. If version is lower than 2.22.2, continue to next checks.
  2. Review JNDI URI usage in JCR configuration
    Search configuration files (repository.xml, repository.xml in conf/ or WEB-INF/ directories) for any InitialContextFactory or other JNDI-related settings, and examine any code that performs JCR lookups using strings that could be user-controlled.
    Affected if JNDI-based JCR lookup is enabled or configured in your environment.
  3. Check if untrusted users can supply JCR lookup strings
    Audit application code that accepts user input and passes it to JCR repository lookups (Repository.login(), Session.getWorkspace(), etc.). Determine if untrusted input reaches these lookup methods.
    Affected if Untrusted or external users can influence the strings passed to JCR lookup operations.

Your environment is affected if Apache Jackrabbit version is below 2.22.2 AND JNDI-based JCR lookup is enabled with untrusted user input able to reach lookup operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.22.2 or later
Fixed in 2.22.2
Interim mitigation

Upgrade to Apache Jackrabbit version 2.22.2 where JNDI-based JCR lookup is disabled by default, and explicitly review any remaining JNDI URI usage.

Recommended fix High confidence

2.22.2

  1. Stop the Apache Jackrabbit application
  2. Backup the current installation and all configuration files
  3. Download Apache Jackrabbit Core version 2.22.2 from the official Apache distribution site (https://jackrabbit.apache.org/downloads.html)
  4. Replace the existing jackrabbit-core JAR file with version 2.22.2
  5. Replace the existing jcr-commons JAR file with version 2.22.2
  6. If your application relies on JNDI URI for JCR lookup, review and test the functionality; JNDI lookup is now disabled by default
  7. Restart the application
  8. Verify the application functions correctly and test JCR lookup functionality
Caveat JCR lookup through JNDI has been disabled by default in 2.22.2; applications relying on this feature will need to explicitly enable it and perform a security review

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jackrabbit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58782 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data