Copyright © 2012 Red Hat, Inc. All rights reserved. Important 2026-07-01T20:02:47 com.mchange/mchange-commons-java: mchange-commons-java: Remote code execution via JNDI injection 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H CWE-502

mchange-commons-java is a Java library of shared utility classes used by mchange projects like the c3p0 connection pool. Prior to version 0.6.0, its JNDI ObjectFactory implementation (com.mchange.v2.naming.JavaBeanObjectFactory) will construct objects of arbitrary classes and initialize "JavaBean"-style properties, which for certain classes enables JNDI injection and "deserialization gadgets." Such initialization is unsafe for some classes: for example, setting the contentType property of a Swing JEditorPane to text/html and its text property to HTML containing a stylesheet <link> will provoke an HTTP GET on an arbitrary URL, potentially from within a trusted security domain. The problem is aggravated by the library's ReferenceIndirector, through which malicious JNDI Reference objects can be smuggled in for dereferencing wherever an application reads a Java-serialized object. This has been resolved in version 0.6.0.

A flaw was found in mchange-commons-java, a Java utility library. This vulnerability allows a remote attacker to achieve arbitrary code execution through Java Naming and Directory Interface (JNDI) injection. The library's JNDI ObjectFactory can construct objects of arbitrary classes and initialize properties, which can be exploited by malicious JNDI Reference objects. This could lead to an attacker executing unauthorized code within the application's security domain.

A flaw was found in mchange-commons-java, a Java utility library primarily used as a dependency of the c3p0 JDBC connection pool. Prior to version 0.6.0, the library's JNDI ObjectFactory implementation (JavaBeanObjectFactory) will construct objects of arbitrary classes and initialize JavaBean-style properties, which for certain classes enables JNDI injection and deserialization gadgets. The problem is aggravated by the library's ReferenceIndirector, through which malicious JNDI Reference objects can be smuggled wherever an application reads a Java-serialized object. Exploitation requires either: (1) an attacker-controllable JNDI lookup name reaching a naming context where the vulnerable ObjectFactory is registered, or (2) a deserialization entry point accepting untrusted Java objects, where ReferenceIndirector serves as a gadget class (similar to Log4Shell-style JNDI injection). All affected Red Hat products ship vulnerable versions (< 0.6.0) of mchange-commons-java as a transitive runtime dependency of c3p0 and Hibernate connection pooling. Upgrading to mchange-commons-java >= 0.6.0 is strongly recommended. Most applications that include mchange-commons-java do so to support the c3p0 JDBC connection pooling library. When upgrading mchange-commons-java, be sure to update c3p0 as well — upgrading to c3p0 >= 0.14.0 will bring in a patched mchange-commons-java transitively. As a general hardening measure, applications should avoid deserializing untrusted Java objects, and restrict JNDI lookups to trusted naming contexts only. Red Hat build of Apache Camel for Spring Boot 4 Affected mchange-commons-java Red Hat build of Apache Camel - HawtIO 4 Affected mchange-commons-java Red Hat build of Debezium 3 Not affected mchange-commons-java Red Hat JBoss Enterprise Application Platform Expansion Pack Affected mchange-commons-java Red Hat Satellite 6 Not affected candlepin Red Hat Satellite 6 Not affected satellite:el8/candlepin streams for Apache Kafka 2 Affected mchange-commons-java https://www.cve.org/CVERecord?id=CVE-2026-55153 https://nvd.nist.gov/vuln/detail/CVE-2026-55153 https://github.com/swaldman/mchange-commons-java/security/advisories/GHSA-h84g-69h7-mw6v