Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-27830

8.0 · HIGH

c3p0, a JDBC Connection pooling library, is vulnerable to attack via maliciously crafted Java-serialized objects and `javax.naming.Reference` instances.

Published Feb 26, 2026CWE-94EPSS 2.04%

Overview

CVE-2026-27830 is a high-severity vulnerability. It was published on February 26, 2026 and has a CVSS 3.1 base score of 8.0 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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<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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

GitHubgithub.com/swaldman/c3p0/commit/e14cbd8166e423e2e9a9d6f08b2add3433492d6eGitHubgithub.com/swaldman/c3p0/security/advisories/GHSA-5476-xc4j-rqcvRefmogwailabs.de/en/blog/2025/02/c3p0-you-little-rascalRefwww.mchange.com/projects/c3p0/#configuring_securityRefwww.mchange.com/projects/c3p0/#security-noteRefaccess.redhat.com/errata/RHSA-2026:18054Refaccess.redhat.com/errata/RHSA-2026:18055Refaccess.redhat.com/errata/RHSA-2026:18059Refaccess.redhat.com/errata/RHSA-2026:28385Refaccess.redhat.com/errata/RHSA-2026:3890

How CyberStrike helps

Frequently asked questions

What is CVE-2026-27830?

CVE-2026-27830 is a high-severity vulnerability. It was published on February 26, 2026 and has a CVSS 3.1 base score of 8.0 (HIGH).

How severe is CVE-2026-27830?

This vulnerability has a CVSS 3.1 base score of 8.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-27830?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-27830?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-27830 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999