# mchange-commons-java: Remote Code Execution via JNDI Reference Resolution

Advisory record · `GHSA-m2cm-222f-qw44`

- **Identifiers:** `GHSA-m2cm-222f-qw44` · `CVE-2026-27727`
- **State:** Confirmed
- **Severity:** CVSS 8.9 High
- **Critical:** No
- **Weakness (CWE):** [CWE-74](https://cwe.mitre.org/data/definitions/74.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md) · [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 25 Feb 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Feb 2026, 18:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.mchange:mchange-commons-java` (Maven): affected `<0.4.0`; fixed in `0.4.0`

## Machine-written summary

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

> mchange-commons-java versions before 0.4.0 include a JNDI implementation that can download and run code from a remote factoryClassLocation. An attacker who can get an application to read a maliciously crafted JNDI Reference or serialized object could cause remote code execution, even where the JDK's own protections are enabled. Upgrade to mchange-commons-java 0.4.0 or later, which gates this functionality behind restrictive configuration defaults. The source lists no workaround other than upgrading.

Written 2 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

- 8.9 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0098, the 62nd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m2cm-222f-qw44)

## Sources

- [GitHub Advisory Database: GHSA-m2cm-222f-qw44](https://github.com/advisories/GHSA-m2cm-222f-qw44)
- [OSV: GHSA-m2cm-222f-qw44](https://osv.dev/vulnerability/GHSA-m2cm-222f-qw44)
- <https://github.com/swaldman/mchange-commons-java/security/advisories/GHSA-m2cm-222f-qw44>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-27727>
- <https://github.com/swaldman/mchange-commons-java>
- <https://mogwailabs.de/en/blog/2025/02/c3p0-you-little-rascal>
- <https://www.mchange.com/projects/c3p0/#configuring_security>
- <https://www.mchange.com/projects/c3p0/#security-note>

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-m2cm-222f-qw44>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m2cm-222f-qw44/>. Everything for agents: <https://agentprime.io/llms.txt>.