🛡️ CVE-2026-27727 — mchange-commons-java

🔴 CVSS 9.8 — Critical ✅ No Known Exploit CWE-502 NVD
9.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

Impact

mchange-commons-java includes code that mirrors early implementations of JNDI functionality, including support for remote factoryClassLocation values, by which code can be downloaded and invoked within a running application. If an attacker can provoke an application to read a maliciously crafted jaxax.naming.Reference or serialized object, they can provoke the download and execution of malicious code.

Implementations of this functionality within the JDK were disabled by default behind a System property that defaults to false, com.sun.jndi.ldap.object.trustURLCodebase. However, since mchange-commons-java includes an independent implementation of JNDI derefencing, libraries (such as c3p0) that resolve references via that implementation could be provoked to download and execute malicious code even after the JDK was hardened.

Patches

Mirroring the JDK patch, mchange-commons-java's JNDI functionality is now gated by configuration parameters that default to restrictive values. Those parameters are documented [here](https://www.mchange.com/projects/c3p0/#configuring_security).

Workarounds

No. Users should upgrade to mchange-commons-java >= 0.4.0. Earlier versions should be avoided on application CLASSPATHs.

References

[c3p0, you little rascal — Hans-Martin Münch](https://mogwailabs.de/en/blog/2025/02/c3p0-you-little-rascal/)

[c3p0 documentation, security note](https://www.mchange.com/projects/c3p0/#security-note)

[c3p0 documentation, configuring security](https://www.mchange.com/projects/c3p0/#configuring_security)

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

Weakness class

CVE-2026-27727 is classified as CWE-502: Deserialization of Untrusted Data. Serialised data from an untrusted source is reconstructed into objects, which can trigger code during the process.

Affected software

CVE-2026-27727 is recorded against 2 packages.

  • com.mchange:mchange-commons-java (fixed in 0.4.0)
  • mchange-commons-java (fixed in 0.4.0)

Timeline and source

Published on 25 February 2026 and last revised on 28 February 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Package)
mogwailabs.de (Web)
www.mchange.com (Web)
www.mchange.com (Web)

Details

Severity HIGH
CVSS Score 9.8
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE CWE-502
Public Exploit ✅ No
Source NVD
Published 2026-02-25
Updated 2026-08-12
Modified 2026-02-28

Affected Packages

Software From version Fixed in
com.mchange:mchange-commons-java — 0.4.0
mchange-commons-java — 0.4.0

Similar Threats

Exploit Protection

Are you running mchange-commons-java?

CVE-2026-27727 carries CVSS 9.8 Critical rating. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-27727 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.