# CVE-2026-55153: mchange-commons-java contains elements susceptible to abuse via JNDI injection and "deserialization gadgets" > Attackers can exploit unsafe JNDI object construction and deserialization gadgets in mchange-commons-java to execute arbitrary code or bypass security controls. - **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Jul 2026 - **Updated:** 6 Jul 2026 - **Also known as:** CLEANSTART-2026-XR11055, CLSA-2026-1786542819, CLSA-2026-1786594683, CLSA-2026-1788238245, ECHO-de0f-2160-8020, GHSA-h84g-69h7-mw6v, UBUNTU-CVE-2026-55153 ## What is CVE-2026-55153? CVE-2026-55153 is a high-severity unsafe deserialization vulnerability in swaldman mchange-commons-java, published on 1 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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 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. Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-470 (Use of Externally-Controlled Input to Select Classes or Code) ## Which versions are affected by CVE-2026-55153? 2 open source packages ship an affected version, including com.mchange:mchange-commons-java. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.mchange:mchange-commons-java` | Maven | All versions | 0.6.0 | | `com.mchange:mchange-commons-java` | Maven | All versions | 0.6.0 | ## How do I fix CVE-2026-55153? Upgrade com.mchange:mchange-commons-java to 0.6.0 or later. ## Is CVE-2026-55153 being exploited? There is no known exploitation of CVE-2026-55153 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-55153 and fix it if it is affected. What it is: CVE-2026-55153 is a high-severity unsafe deserialization vulnerability in swaldman mchange-commons-java, published on 1 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-55153 in the wild and no public exploit code. Affected packages and fixed versions: - com.mchange:mchange-commons-java (Maven): affected all versions; fixed in 0.6.0 - com.mchange:mchange-commons-java (Maven): affected all versions; fixed in 0.6.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-55153/ (Markdown: https://insights.sbomify.com/CVE-2026-55153/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55153 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55153 - OSV: https://osv.dev/vulnerability/CVE-2026-55153 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-55153/ Summaries are generated and may contain mistakes; the official description above is the record.