mchange-commons-java: Remote Code Execution via JNDI Reference Resolution
Published Feb 25, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
mchange-commons-java: Remote Code Execution via JNDI Reference Resolution
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
mchange-commons-java 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.
Potential impact
mchange-commons-java 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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Security advisory ↗
- https://mogwailabs.de/en/blog/2025/02/c3p0-you-little-rascal ↗
- https://www.mchange.com/projects/c3p0/#configuring_security ↗
- https://www.mchange.com/projects/c3p0/#security-note ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
Record history
Published Feb 25, 2026 · Last refreshed Nov 3, 2026