# Improper Input Validation in Drools and jBPM

Advisory record · `GHSA-6qx9-rf9g-7jmr`

- **Identifiers:** `GHSA-6qx9-rf9g-7jmr` · `CVE-2014-8125`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 17 May 2022
- **Updated:** 7 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 04:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.drools:drools-core` (Maven): affected `<6.2.0.Final`; fixed in `6.2.0.Final`
- `org.jbpm:jbpm-bpmn2` (Maven): affected `<6.2.0.Final`; fixed in `6.2.0.Final`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Drools (org.drools:drools-core) and jBPM (org.jbpm:jbpm-bpmn2) versions before 6.2.0.Final are affected. A remote attacker can supply a crafted BPMN2 file to exploit an XML external entity (XXE) flaw, which can allow reading arbitrary files and may have other unspecified impact. Upgrade drools-core and jbpm-bpmn2 to 6.2.0.Final or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.026, the 85th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6qx9-rf9g-7jmr)

## Sources

- [GitHub Advisory Database: GHSA-6qx9-rf9g-7jmr](https://github.com/advisories/GHSA-6qx9-rf9g-7jmr)
- [OSV: GHSA-6qx9-rf9g-7jmr](https://osv.dev/vulnerability/GHSA-6qx9-rf9g-7jmr)
- <https://nvd.nist.gov/vuln/detail/CVE-2014-8125>
- <https://github.com/droolsjbpm/drools/commit/c48464c3b246e6ef0d4cd0dbf67e83ccd532c6d3>
- <https://github.com/droolsjbpm/jbpm/commit/713e8073ecf45623cfc5c918c5cbf700203f46e5>
- <https://bugzilla.redhat.com/show_bug.cgi?id=1169553>
- <http://rhn.redhat.com/errata/RHSA-2015-0850.html>
- <http://rhn.redhat.com/errata/RHSA-2015-0851.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6qx9-rf9g-7jmr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6qx9-rf9g-7jmr/>. Everything for agents: <https://agentprime.io/llms.txt>.
