How severe is CVE-2015-1833?

No CVSS score has been assigned to CVE-2015-1833 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-1833?

CVE-2015-1833 affects the following packages: org.apache.jackrabbit:jackrabbit-core (Maven), org.apache.jackrabbit:jackrabbit-core (Maven), org.apache.jackrabbit:jackrabbit-core (Maven), org.apache.jackrabbit:jackrabbit-core (Maven), org.apache.jackrabbit:jackrabbit-core (Maven), org.apache.jackrabbit:jackrabbit-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-1833?

Update org.apache.jackrabbit:jackrabbit-core to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1833 is resolved across your whole dependency graph.

How do I detect CVE-2015-1833 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.jackrabbit:jackrabbit-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-1833 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2015-1833?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2015-1833 can be triaged on real exposure rather than presence alone.

Is CVE-2015-1833 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2015-1833, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-1833?

CVE-2015-1833 has an EPSS (Exploit Prediction Scoring System) score of 55.0%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2015-1833?

CVE-2015-1833 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-1833 published, and has it been updated?

CVE-2015-1833 was published on May 29, 2015 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2015-1833 — jackrabbit-core

Fix: apache/jackrabbit@17e9f68

CVE-2015-1833 is a Improper Input Validation vulnerability in org.apache.jackrabbit:jackrabbit-core. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.jackrabbit:jackrabbit-core — see the affected versions and patch details below.

Improper Input Validation in Apache Jackrabbit

Also known asGHSA-9284-j4c9-779q

Published

May 29, 2015

Updated

Apr 16, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

2 known

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

55.0%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

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.

Real-World Exposure

6 pkgs affected

☕org.apache.jackrabbit:jackrabbit-core☕org.apache.jackrabbit:jackrabbit-core☕org.apache.jackrabbit:jackrabbit-core☕org.apache.jackrabbit:jackrabbit-core☕org.apache.jackrabbit:jackrabbit-core☕org.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

XML external entity (XXE) vulnerability in Apache Jackrabbit before 2.0.6, 2.2.x before 2.2.14, 2.4.x before 2.4.6, 2.6.x before 2.6.6, 2.8.x before 2.8.1, and 2.10.x before 2.10.1 allows remote attackers to read arbitrary files and send requests to intranet servers via a crafted WebDAV request.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.jackrabbit:jackrabbit-core`	all versions	2.0.6`org.apache.jackrabbit:jackrabbit-core:2.0.6`
☕Maven	`org.apache.jackrabbit:jackrabbit-core`	≥ 2.2.0&&< 2.2.14	2.2.14`org.apache.jackrabbit:jackrabbit-core:2.2.14`
☕Maven	`org.apache.jackrabbit:jackrabbit-core`	≥ 2.4.0&&< 2.4.6	2.4.6`org.apache.jackrabbit:jackrabbit-core:2.4.6`
☕Maven	`org.apache.jackrabbit:jackrabbit-core`	≥ 2.6.0&&< 2.6.6	2.6.6`org.apache.jackrabbit:jackrabbit-core:2.6.6`
☕Maven	`org.apache.jackrabbit:jackrabbit-core`	≥ 2.8.0&&< 2.8.1	2.8.1`org.apache.jackrabbit:jackrabbit-core:2.8.1`
☕Maven	`org.apache.jackrabbit:jackrabbit-core`	≥ 2.10.0&&< 2.10.1	2.10.1`org.apache.jackrabbit:jackrabbit-core:2.10.1`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-37110webappsjava

Apache JackRabbit - WebDAV XML External Entity

by Mikhail Egorov · May 26, 2015

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.jackrabbit:jackrabbit-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.jackrabbit:jackrabbit-core to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1833 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2015-1833 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-1833 in your dependencies?

O3 Security finds CVE-2015-1833 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works