How severe is CVE-2015-1832?

CVE-2015-1832 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-1832?

CVE-2015-1832 affects the following packages: org.apache.derby:derby (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-1832?

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

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

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

No public exploit code has been indexed for CVE-2015-1832 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2015-1832 has an EPSS (Exploit Prediction Scoring System) score of 12.2%, placing it in the 96th 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. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2015-1832?

CVE-2015-1832 is classified as CWE-399 (CWE-399), XML External Entity (XXE) (CWE-611). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2015-1832 was published on October 3, 2016 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

CRITICAL severity

CVE-2015-1832 — derby

CRITICAL

CVE-2015-1832 is a critical-severity (CVSS 9.1) CWE-399 vulnerability in org.apache.derby:derby. EPSS puts its 30-day exploitation probability at 12.2% (96th percentile). A fix is available for org.apache.derby:derby — see the affected versions and patch details below.

Improper Restriction of XML External Entity Reference in Apace Derby

Also known asGHSA-wr69-g62g-2r9h

Published

Oct 3, 2016

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

12.2%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.apache.derby:derby

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 the SqlXmlUtil code in Apache Derby before 10.12.1.1, when a Java Security Manager is not in place, allows context-dependent attackers to read arbitrary files or cause a denial of service (resource consumption) via vectors involving XmlVTI and the XML datatype.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.derby:derby`	all versions	10.12.1.1`org.apache.derby:derby:10.12.1.1`

Affected Products

1 product · 20 configurations

Application

derbyapache

20 versions

10.1.1.010.1.2.110.1.3.110.2.1.610.2.2.010.3.3.010.4.1.310.4.2.010.5.1.110.5.3.010.6.1.010.6.2.1

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.derby:derby, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.derby:derby to 10.12.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1832 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-1832 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works