dbcve.org
Mchange Commons JavaApplication · Mchange

CVE-2026-27727

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 0.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
mchange-commons-java, a library that provides Java utilities, 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. Mirroring the JDK patch, mchange-commons-java's JNDI functionality is gated by configuration parameters that default to restrictive values starting in version 0.4.0. No known workarounds are available. Versions prior to 0.4.0 should be avoided on application CLASSPATHs.

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 confidence

mchange-commons-java contains an independent JNDI implementation that supports remote factoryClassLocation resolution, allowing malicious Reference or serialized objects to trigger arbitrary code download and execution. This bypasses JDK hardening because the library implements its own dereferencing logic rather than using JDK code. Versions 0.4.0+ gate this functionality behind restrictive configuration defaults.

MitigationUpgrade mchange-commons-java to version 0.4.0 or later, which applies restrictive defaults to JNDI functionality. Test thoroughly to ensure the new defaults do not break legitimate JNDI operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mchange Commons JavaApplication
Affected:< 0.4.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate mchange-commons-java in your application
    Search your application dependencies (Maven pom.xml, Gradle build files, lib/ folders, WAR files) for mchange-commons-java. Also check nested JARs using 'jar tf' or unzip -l commands.
    Affected if mchange-commons-java is present in your classpath or dependencies
  2. Identify the installed version
    Examine the JAR filename for version (e.g., mchange-commons-java-0.3.x.jar) or inspect the manifest file inside the JAR. In Maven, run 'mvn dependency:tree | grep mchange-commons-java' to see the resolved version.
    Affected if The version is lower than 0.4.0 or no version is specified (indicating an old inclusion)
  3. Check for JNDI usage in your application code
    Search source code for imports or usage of javax.naming.Reference, javax.naming.StringRefAddr, or any code that creates JNDI references. Also check configuration files for JNDI resource definitions.
    Affected if Your application creates or processes javax.naming.Reference objects or deserializes objects from JNDI lookups
  4. Inspect application serialization paths
    Review code that deserializes objects from external sources, especially if those sources could be controlled via JNDI lookup results. Look for ObjectInputStream usage with data from JNDI contexts.
    Affected if Your application deserializes data retrieved from JNDI lookups without validation
  5. Verify JDK JNDI security settings
    Check if your JVM is running with -Dcom.sun.jndi.ldap.object.trustURLCodebase=false (this mitigates JDK JNDI but does NOT protect against mchange-commons-java's own JNDI implementation).
    Affected if Your application relies solely on JDK JNDI protections without accounting for mchange-commons-java's independent JNDI handling

Your environment is affected if mchange-commons-java version below 0.4.0 is present in the classpath AND your application uses JNDI features that could trigger the library's custom dereferencing logic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.4.0 or later
Fixed in 0.4.0
Vendor patch github.com →
Interim mitigation

Upgrade mchange-commons-java to version 0.4.0 or later, which applies restrictive defaults to JNDI functionality. Test thoroughly to ensure the new defaults do not break legitimate JNDI operations.

Recommended fix High confidence

0.4.0 or later

  1. Identify all dependencies that include mchange-commons-java version < 0.4.0
  2. Upgrade mchange-commons-java to version 0.4.0 or later in all affected applications
  3. Rebuild and redeploy applications with the updated dependency
  4. Verify that the upgraded library is correctly loaded at runtime

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mchange Commons Java Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27727 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27727 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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