CVE-2026-55153
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedmchange-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe mchange-commons-java library's JNDI ObjectFactory (JavaBeanObjectFactory) insecurely instantiates arbitrary Java classes and initializes their properties, enabling JNDI injection and deserialization gadget attacks. Attackers can trigger harmful operations like arbitrary HTTP requests (e.g., via JEditorPane) or smuggle malicious JNDI References through the ReferenceIndirector for deserialization when applications read serialized objects.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify mchange-commons-java in your dependenciesSearch your project dependencies (Maven pom.xml, Gradle build.gradle, or compiled JARs in classpath) for 'mchange-commons-java' or 'com.mchange:mchange-commons-java'. Run: grep -r 'mchange-commons-java' . or list all JARs in your lib/ or WEB-INF/lib/ directory.Affected if The library is present and its version is below 0.6.0 (e.g., 0.5.x, 0.4.x, etc.)
-
Check JNDI ObjectFactory usageSearch your codebase for JNDI lookup operations that use JavaBeanObjectFactory or any custom ObjectFactory implementing javax.naming.spi.ObjectFactory. Look for Context.lookup() calls interacting with deserialized data or user-controlled JNDI names.Affected if Your application performs JNDI lookups using objects from mchange-commons-java or deserializes data from untrusted sources that could contain JNDI References
-
Inspect deserialization pathsReview code that deserializes objects from external sources (ObjectInputStream, JMX, RMI, JMS, file uploads, network protocols). Search for patterns like 'ObjectInputStream', 'readObject', 'JNDI', 'Reference', 'ReferenceIndirector'.Affected if Your application deserializes objects from untrusted sources and has mchange-commons-java in the classpath
-
Verify HTTP request gadget availabilityCheck if JEditorPane or similar Swing components are accessible in your runtime classpath alongside mchange-commons-java. These are used as gadget chains to trigger arbitrary HTTP requests.Affected if JEditorPane (or java.swing classes) are on the classpath and mchange-commons-java version is below 0.6.0 with JNDI/deserialization exposure
-
Confirm vulnerability via version checkIf mchange-commons-java is found, determine its exact version from Maven/Gradle metadata, JAR manifest, or by inspecting the JAR filename. Compare against the fixed version 0.6.0.Affected if The installed version is any version prior to 0.6.0 (e.g., 0.5.12, 0.5.0, 0.4.0)
You are affected if mchange-commons-java version below 0.6.0 is present in your environment and your application performs JNDI lookups or deserializes data from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade mchange-commons-java to version 0.6.0 or later; if upgrade is not feasible, audit and restrict JNDI lookups and deserialization of untrusted data.
mchange-commons-java version 0.6.0
- Identify all dependencies on mchange-commons-java in the project (check pom.xml, build.gradle, or other dependency management files)
- Locate the current version of mchange-commons-java being used
- Update the dependency version to 0.6.0 or later
- Run dependency resolution to ensure the new version is correctly pulled
- Rebuild the application
- Test the application to verify functionality is maintained after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55153 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-55153 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data