Deserialization of Untrusted Data Affecting com.mchange:c3p0 package, versions [,0.14.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-COMMCHANGE-17816596
- published4 Jul 2026
- disclosed30 Jun 2026
- creditUnknown
Introduced: 30 Jun 2026
NewCVE-2026-55223 (opens in a new tab)How to fix?
Upgrade com.mchange:c3p0 to version 0.14.0 or higher.
Overview
com.mchange:c3p0 is a mature, highly concurrent JDBC Connection pooling library, with support for caching and reuse of PreparedStatements.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the deserialization process. An attacker can execute arbitrary code by delivering a crafted serialized object that, when deserialized, triggers automatic property resolution and invokes vulnerable JDBC driver methods. This is only exploitable if all of the following conditions are met: a vulnerable version is present on the application classpath, a susceptible JDBC driver is available, a carrier library such as Apache Commons BeanUtils is used to auto-read JavaBean properties during deserialization, and there is a deserialization entry point that processes attacker-controlled data.
Workaround
This vulnerability can be mitigated by running applications on Java 16 or later, removing Apache Commons BeanUtils from the classpath if not required, or ensuring the application does not deserialize untrusted input from network sources.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.