VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.mchange:c3p0: vulnerability history, versions and safety

com.mchange:c3p0 is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 42 releases, from Jan 2019 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 23 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all com.mchange:c3p0 vulnerabilities

Vulert verdict on com.mchange:c3p0 0.14.2 i

Updated on 23 Oct 2026

Good news: 0.14.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 68/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 0.14.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.14.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.14.2 — unaffected i
  • Vulnerabilities on record 4 over 7 years · 2 in the last year i
  • Latest disclosure 23 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 50 packages i
  • Stars 1,318 i
  • OpenSSF scorecard 2/10 i
  • Last release 1 month ago i
  • Licence LGPL-2.1-or-later i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for com.mchange:c3p0, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.14.2 04 Sep 2026 none LGPL-2.1-or-later — Details →
0.14.1 09 Jun 2026 none LGPL-2.1-or-later — Details →
0.14.0 03 Jun 2026 none LGPL-2.1-or-later — Details →
0.13.0 23 Apr 2026 M1 LGPL-2.1-or-later Yes Details →
0.12.0 22 Feb 2026 M1 LGPL-2.1-or-later Yes Details →
0.11.2 23 Jun 2025 H1 M1 LGPL-2.1-or-later Yes Details →
0.11.1 29 May 2025 H1 M1 LGPL-2.1-or-later Yes Details →
0.11.0 23 Apr 2025 H1 M1 LGPL-2.1-or-later Yes Details →
0.11.0-pre2 20 Feb 2025 H1 M1 LGPL-2.1-or-later Yes Details →
0.11.0-pre1 12 Feb 2025 H1 M1 LGPL-2.1-or-later Yes Details →
0.10.2 31 Jan 2025 H1 M1 LGPL-2.1-or-later Yes Details →
0.10.1 07 May 2024 H1 M1 LGPL-2.1-or-later Yes Details →
0.10.0 03 Mar 2024 H1 M1 LGPL-2.1-or-later Yes Details →
0.10.0-pre7 03 Mar 2024 H1 M1 LGPL-2.1-or-later Yes Details →
0.10.0-pre6 29 Feb 2024 H1 M1 LGPL-2.1-or-later Yes Details →
0.10.0-pre5 26 Feb 2024 H1 M1 LGPL-2.1-or-later Yes Details →
0.10.0-pre4 23 Feb 2024 H1 M1 LGPL-2.1-or-later Yes Details →
0.10.0-pre3 18 Feb 2024 H1 M1 LGPL-2.1-only Yes Details →
0.10.0-pre2 16 Feb 2024 H1 M1 LGPL-2.1-only Yes Details →
0.10.0-pre1 15 Feb 2024 H1 M1 LGPL-2.1-only Yes Details →
0.9.5.5 12 Dec 2019 H1 M1 LGPL-2.1 Yes Details →
0.9.5.4 24 Mar 2019 H1 M1 LGPL-2.1 Yes Details →
0.9.5.3 27 Jan 2019 H2 M1 LGPL-2.1 Yes Details →
0.9.5.2 09 Dec 2015 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5.1 16 Jun 2015 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5 02 Jan 2015 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre10 06 Nov 2014 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre9 08 Oct 2014 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre8 04 Apr 2014 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre7 23 Mar 2014 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre6 07 Dec 2013 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre5 23 Oct 2013 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre4 23 Aug 2013 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre3 22 May 2013 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre2 23 Apr 2013 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.5-pre1 20 Mar 2013 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2.1 20 Mar 2013 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2 09 Feb 2013 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2-pre8 19 Dec 2012 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2-pre7 13 Dec 2012 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2-pre6 22 Nov 2012 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2-pre5 29 Sep 2012 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2-pre4 17 Jun 2012 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2-pre3 16 Jun 2012 C1 H2 M1 LGPL-2.1 Yes Details →
0.9.2-pre2-RELEASE 18 May 2012 C1 H2 M1 LGPL-2.1 Yes Details →

All 45 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for com.mchange:c3p0

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-20433: XML External Entity Reference in mchange:c3p0 9.8 critical 0.9.5.3 07 Jan 2019
CVE-2026-27830: c3p0 Remote Code Execution via Unsafe Deserialization 8.9 high 0.12.0 25 Feb 2026
CVE-2019-5427: Billion laughs attack in c3p0 7.5 high 0.9.5.4 23 Apr 2019
CVE-2026-55223: c3p0 JDBC DataSource Vulnerability Leading to Deserialization Attacks 6.3 medium 0.14.0 23 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About com.mchange:c3p0

Is com.mchange:c3p0 safe to use?

Vulert records 4 vulnerabilities for com.mchange:c3p0 in Maven: 1 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is com.mchange:c3p0's Vulert package health score?

Vulert scores com.mchange:c3p0 68/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of com.mchange:c3p0 affected?

No. 0.14.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of com.mchange:c3p0 should I use?

0.14.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does com.mchange:c3p0 have?

4 vulnerabilities are recorded for com.mchange:c3p0 in the Maven ecosystem: 1 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.mchange:c3p0 vulnerabilities disclosed?

2 vulnerabilities were recorded for com.mchange:c3p0 in the last 12 months, and the oldest entry in this database dates to 07 Jan 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of com.mchange:c3p0 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor com.mchange:c3p0 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.mchange:c3p0 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.