How severe is CVE-2014-8125?

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

Which packages are affected by CVE-2014-8125?

CVE-2014-8125 affects the following packages: org.drools:drools-core (Maven), org.jbpm:jbpm-bpmn2 (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-8125?

Update org.drools:drools-core to 6.2.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-8125 is resolved across your whole dependency graph.

How do I detect CVE-2014-8125 in my Maven dependencies?

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

How do I mitigate CVE-2014-8125 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.

Is CVE-2014-8125 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-8125 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-2014-8125?

CVE-2014-8125 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 86th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2014-8125 published, and has it been updated?

CVE-2014-8125 was published on May 17, 2022 and was last updated on December 7, 2024. 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-2014-8125 — drools-core

Fix: droolsjbpm/drools@c48464c

CVE-2014-8125 is a security vulnerability in org.drools:drools-core. A fix is available for org.drools:drools-core — see the affected versions and patch details below.

Improper Input Validation in Drools and jBPM

Published

May 17, 2022

Updated

Dec 7, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.drools:drools-core☕org.jbpm:jbpm-bpmn2

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 Drools and jBPM before 6.2.0 allows remote attackers to read arbitrary files or possibly have other unspecified impact via a crafted BPMN2 file.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.drools:drools-core`	all versions	6.2.0.Final`org.drools:drools-core:6.2.0.Final`
☕Maven	`org.jbpm:jbpm-bpmn2`	all versions	6.2.0.Final`org.jbpm:jbpm-bpmn2:6.2.0.Final`

Affected Products

2 products · 2 configurations

Application

droolsredhat

≤ 6.1.0

range

Application

jbpmredhat

≤ 6.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.drools:drools-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.drools:drools-core to 6.2.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-8125 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 5; and Red Hat JBoss Enterprise SOA Platform 4 and 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future…

Product	Fixed in	Advisory
Red Hat JBoss BPMS 6.0	`jbpm`	RHSA-2015:0851
Red Hat JBoss BRMS 6.0	`jbpm`	RHSA-2015:0850

Frequently Asked Questions

XML external entity (XXE) vulnerability in Drools and jBPM before 6.2.0 allows remote attackers to read arbitrary files or possibly have other unspecified impact via a crafted BPMN2 file.

O3 Security · Impact-Aware SCA

Is CVE-2014-8125 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works