Answer in brief
CVE-2026-27830 records a High severity (CVSS 8.9) vulnerability in c3p0 vulnerable to Remote Code Execution via unsafe deserialization of userOverridesAsString property. The current sources do not mark it as known exploited. The current feed maps swaldman/c3p0 (generic), Red Hat/c3p0 (generic), Red Hat/c3p0/c3p0 (generic), Red Hat/com.mchange/c3p0 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps swaldman/c3p0 (generic), Red Hat/c3p0 (generic), Red Hat/c3p0/c3p0 (generic), Red Hat/com.mchange/c3p0 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| swaldman/c3p0generic | <0.12.0 | 0.12.0 |
| Red Hat/c3p0generic | * | Not reported |
| Red Hat/c3p0/c3p0generic | * | Not reported |
| Red Hat/com.mchange/c3p0generic | * | Not reported |
| Red Hat/com.mchange.v2.c3p0/c3p0generic | * | Not reported |
| Red Hat/org.hibernate/hibernate-c3p0generic | * | Not reported |
| Red Hat/org.hibernate.orm/hibernate-c3p0generic | * | Not reported |
Published upstream
Feb 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
c3p0, a JDBC Connection pooling library, is vulnerable to attack via maliciously crafted Java-serialized objects and `javax.naming.Reference` instances. Several c3p0 `ConnectionPoolDataSource` implementations have a property called `userOverridesAsString` which conceptually represents a `Map<String,Map<String,String>>`. Prior to v0.12.0, that property was maintained as a hex-encoded serialized object. Any attacker able to reset this property, on an existing `ConnectionPoolDataSource` or via maliciously crafted serialized objects or `javax.naming.Reference` instances could be tailored execute unexpected code on the application's `CLASSPATH`. The danger of this vulnerability was strongly magnified by vulnerabilities in c3p0's main dependency, mchange-commons-java. This library includes code that mirrors early implementations of JNDI functionality, including ungated support for remote `factoryClassLocation` values. Attackers could set c3p0's `userOverridesAsString` hex-encoded serialized objects that include objects "indirectly serialized" via JNDI references. Deserialization of those objects and dereferencing of the embedded `javax.naming.Reference` objects could provoke download and execution of malicious code from a remote `factoryClassLocation`. Although hazard presented by c3p0's vulnerabilites are exarcerbated by vulnerabilities in mchange-commons-java, use of Java-serialized-object hex as the format for a writable Java-Bean property, of objects that may be exposed across JNDI interfaces, represents a serious independent fragility. The `userOverridesAsString` property of c3p0 `ConnectionPoolDataSource` classes has been reimplemented to use a safe CSV-based format, rather than rely upon potentially dangerous Java object deserialization. c3p0-0.12.0+ and above depend upon mchange-commons-java 0.4.0+, which gates support for remote `factoryClassLocation` values by configuration parameters that default to restrictive values. c3p0 additionally enforces the new mchange-commons-java `com.mchange.v2.naming.nameGuardClassName` to prevent injection of unexpected, potentially remote JNDI names. There is no supported workaround for versions of c3p0 prior to 0.12.0.
Quoted source text, attributed separately from HOL analysis.