# CVE-2026-27830: c3p0 vulnerable to Remote Code Execution via unsafe deserialization of userOverridesAsString property > Attackers can execute arbitrary code by exploiting unsafe deserialization of the userOverridesAsString property in the c3p0 JDBC connection pooling library. - **Severity:** High 8.9 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA: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:** 26 Feb 2026 - **Updated:** 15 Sep 2026 - **Also known as:** CLSA-2026-1784077471, CLSA-2026-1788527318, CLSA-2026-1789372000, DEBIAN-CVE-2026-27830, ECHO-3f0a-9661-fafe, GHSA-5476-xc4j-rqcv, MINI-287g-62hf-xh76, OESA-2026-1691, UBUNTU-CVE-2026-27830 ## What is CVE-2026-27830? CVE-2026-27830 is a high-severity unsafe deserialization vulnerability in swaldman c3p0, published on 26 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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>`. 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. Weakness: CWE-94 (Improper Control of Generation of Code), CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2026-27830? 2 open source packages ship an affected version, including com.mchange:c3p0. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.mchange:c3p0` | Maven | All versions | 0.12.0 | | `com.mchange:c3p0` | Maven | All versions | 0.12.0 | ## How do I fix CVE-2026-27830? Upgrade com.mchange:c3p0 to 0.12.0 or later. ## Is CVE-2026-27830 being exploited? There is no known exploitation of CVE-2026-27830 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-27830 and fix it if it is affected. What it is: CVE-2026-27830 is a high-severity unsafe deserialization vulnerability in swaldman c3p0, published on 26 Feb 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-27830 in the wild and no public exploit code. Affected packages and fixed versions: - com.mchange:c3p0 (Maven): affected all versions; fixed in 0.12.0 - com.mchange:c3p0 (Maven): affected all versions; fixed in 0.12.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-27830/ (Markdown: https://insights.sbomify.com/CVE-2026-27830/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27830 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27830 - OSV: https://osv.dev/vulnerability/CVE-2026-27830 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-27830/ Summaries are generated and may contain mistakes; the official description above is the record.