mchange-commons-java contains elements susceptible to abuse via JNDI injection and "deserialization gadgets"
CVE-2026-55153GHSA-h84g-69h7-mw6v
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (com.mchange:mchange-commons-java 0.6.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven com.mchange:mchange-commons-java
- Affected
- < 0.6.0
- Fixed in
- 0.6.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-h84g-69h7-mw6v lists affected ranges: Maven com.mchange:mchange-commons-java >=0 <0.6.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-h84g-69h7-mw6v lists affected ranges: Maven com.mchange:mchange-commons-java >=0 <0.6.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.1 · CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-55153: 0.19% estimated exploitation activity in the next 30 days; percentile 9.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact Prior to version 0.6.0, mchange-commons-java includes a JNDI ObjectFactory implementation (com.mchange.v2.naming.JavaBeanObjectFactory) willing to construct objects of arbitrary classes and initialize "JavaBean"-style properties. There are classes for which this kind of initialization is unsafe. For example, setting the "contentType" property of a Swing JEditorPane to text/html and the "text" property to HTML containing a stylesheet <link> will provoke an HTTP GET on an arbitrary URL, potentially from within a trusted security domain. This issue is aggravated by mchange-commons-java's ReferenceIndirector, by which malicious JNDI Reference objects could be smuggled in for dereferencing by applications anywhere a Java-serialized object might be read. Prior to version 0.5.0, the same mchange-commons-java ObjectFactory would interpret BinaryRefAddress elements as Java-serialized objects, and deserialize unexpected objects that potentially execute malicious behavior on…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-h84g-69h7-mw6v
- Revision 1 · created ·
Published from osv record GHSA-h84g-69h7-mw6v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-55153 Advisory: mchange-commons-java contains elements susceptible to abuse via JNDI injection and "deserialization gadgets" IDs: CVE-2026-55153, GHSA-h84g-69h7-mw6v Record: https://patchnext.com/advisories/cve-2026-55153 (revision 2, source checked 26 Oct 2026, 16:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: com.mchange:mchange-commons-java 0.6.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven com.mchange:mchange-commons-java: affected < 0.6.0; fixed in 0.6.0 ## Suggested inspection (read-only) - Maven com.mchange:mchange-commons-java: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on com.mchange:mchange-commons-java. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-h84g-69h7-mw6v (OSV record GHSA-h84g-69h7-mw6v lists affected ranges: Maven com.mchange:mchange-commons-java >=0 <0.6.0 (fixed)) - Verified: https://github.com/advisories/GHSA-h84g-69h7-mw6v (GitHub-reviewed advisory GHSA-h84g-69h7-mw6v lists affected ranges: Maven com.mchange:mchange-commons-java >=0 <0.6.0) Commands are suggestions: review each one before running it.
Loading voting…