CVE-2026-55223

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

c3p0 is a JDBC Connection pooling library. In versions prior to 0.14.0, c3p0 in combination with other libraries, can compose to a "sink" for deserialization gadgets. The JDBC spec's DataSource.getConnection() and ConnectionPoolDataSource.getPooledConnection() match the getXXX() form, so JavaBean libraries treat them as "properties" assumed safe while they actually call into JDBC drivers. Attackers can thus craft malicious DataSource objects whose property lookups invoke vulnerable drivers, then smuggle them in serialized form to where an application deserializes and auto-resolves bean properties — triggering the attack. This requires a susceptible DataSource/ConnectionPoolDataSource and JDBC driver on the CLASSPATH, plus a carrier that auto-looks-up JavaBean properties on = deserialization, most commonly a collection paired with an Apache commons-beanutils Comparator that sorts by bean properties. c3p0 supplied that susceptible DataSource/ConnectionPoolDataSource, which was an essential component of the trigger. This issue has been fixed in version 0.14.0.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 1, 2026
Patch available. Sources: github_commit, github.
githubMentions a patch (unverified)

c3p0 prior to 0.14.0 can, in combination with other libraries, compose to a "sink" for deserialization gadgets · Advisory · swaldman/c3p0 · GitHub

https://github.com/swaldman/c3p0/security/advisories/GHSA-w6w4-rjh9-9r58
github_commit

commit 7b022c4b6694 (swaldman/c3p0)

Fix landed in swaldman/c3p0 commit 7b022c4b6694 — awaiting tagged release

https://github.com/swaldman/c3p0/commit/7b022c4b6694dabc6204254dc917af9c38f2cb27

Vendor Advisories for CVE-2026-55223(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibc3p0-java-doc (0.9.1.2-11ubuntu0.1~esm1) @ resolute2026-09-23ubuntu
redhatc3p02026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
c3p00.9.1.2-10, 0.9.1.2-10.1, 0.9.1.2-10.1~deb12u1, 0.9.1.2-11
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
c3p00.9.1.2-10, 0.9.1.2-10.1, 0.9.1.2-10.1~deb12u1, 0.9.1.2-11
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
c3p00.9.1.2-10.1, 0.9.1.2-11
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
c3p00.9.1.2-10.1, 0.9.1.2-11
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.mchange:c3p00.10.0 ... 0.9.5.5 (42 versions)
  • every version up to 0.14.0: fixed in 0.14.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 154 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 07:05 UTCEG score recompute
  18. 2026-09-23 07:05 UTCVendor advisory
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 06:40 UTCEG score recompute
  22. 2026-09-18 06:40 UTCVendor advisory
  23. 2026-09-17 19:31 UTCEPSS rescore
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 75 more
  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-13 14:21 UTCEG score recompute
  4. 2026-09-13 14:21 UTCVendor advisory
  5. 2026-09-12 14:54 UTCEG score recompute
  6. 2026-09-12 14:54 UTCVendor advisory
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 05:05 UTCEG score recompute
  13. 2026-09-06 05:05 UTCVendor advisory
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 17:15 UTCEG score recompute
  20. 2026-08-30 17:15 UTCVendor advisory
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 22:32 UTCEG score recompute
  24. 2026-08-27 22:32 UTCVendor advisory
  25. 2026-08-27 14:25 UTCEPSS rescore
  26. 2026-08-26 14:46 UTCEPSS rescore
  27. 2026-08-25 13:49 UTCEPSS rescore
  28. 2026-08-25 06:02 UTCEG score recompute
  29. 2026-08-25 06:02 UTCVendor advisory
  30. 2026-08-24 06:37 UTCVendor advisory
  31. 2026-08-23 07:06 UTCEG score recompute
  32. 2026-08-23 07:06 UTCVendor advisory
  33. 2026-08-23 00:19 UTCEPSS rescore
  34. 2026-08-22 07:42 UTCEG score recompute
  35. 2026-08-22 07:42 UTCVendor advisory
  36. 2026-08-21 23:49 UTCEPSS rescore
  37. 2026-08-21 04:42 UTCEG score recompute
  38. 2026-08-21 04:42 UTCVendor advisory
  39. 2026-08-20 22:55 UTCEPSS rescore
  40. 2026-08-20 04:57 UTCEG score recompute
  41. 2026-08-20 04:57 UTCVendor advisory
  42. 2026-08-19 17:04 UTCEPSS rescore
  43. 2026-08-18 22:33 UTCEG score recompute
  44. 2026-08-18 22:33 UTCVendor advisory
  45. 2026-08-18 13:48 UTCEPSS rescore
  46. 2026-08-17 13:47 UTCEPSS rescore
  47. 2026-08-17 09:18 UTCEG score recompute
  48. 2026-08-17 09:18 UTCVendor advisory
  49. 2026-08-16 14:56 UTCEPSS rescore
  50. 2026-08-16 09:55 UTCEG score recompute
  51. 2026-08-16 09:55 UTCVendor advisory
  52. 2026-08-16 02:14 UTCEPSS rescore
  53. 2026-08-15 10:32 UTCEG score recompute
  54. 2026-08-15 10:32 UTCVendor advisory
  55. 2026-08-15 01:30 UTCEPSS rescore
  56. 2026-08-14 11:08 UTCEG score recompute
  57. 2026-08-14 11:08 UTCVendor advisory
  58. 2026-08-13 22:00 UTCEPSS rescore
  59. 2026-08-13 11:45 UTCEG score recompute
  60. 2026-08-12 13:51 UTCEPSS rescore
  61. 2026-08-12 12:20 UTCEG score recompute
  62. 2026-08-11 12:54 UTCEG score recompute
  63. 2026-08-11 00:00 UTCEPSS rescore
  64. 2026-08-09 14:02 UTCEG score recompute
  65. 2026-08-09 13:46 UTCEPSS rescore
  66. 2026-08-08 16:37 UTCEPSS rescore
  67. 2026-08-08 14:39 UTCEG score recompute
  68. 2026-08-06 15:52 UTCEG score recompute
  69. 2026-08-06 13:47 UTCEPSS rescore
  70. 2026-08-05 19:17 UTCEPSS rescore
  71. 2026-08-05 16:26 UTCEG score recompute
  72. 2026-08-04 15:10 UTCEPSS rescore
  73. 2026-08-04 14:35 UTCEG score recompute
  74. 2026-08-04 10:39 UTCEPSS rescore
  75. 2026-08-03 13:29 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55223?
CVE-2026-55223 is a medium vulnerability published on June 30, 2026. c3p0 is a JDBC Connection pooling library. In versions prior to 0.14.0, c3p0 in combination with other libraries, can compose to a "sink" for deserialization gadgets. The JDBC spec's DataSource.getConnection() and ConnectionPoolDataSource.getPooledConnection() match the getXXX() form, so JavaBean…
When was CVE-2026-55223 disclosed?
CVE-2026-55223 was first published on June 30, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55223 actively exploited?
CVE-2026-55223 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55223?
CVE-2026-55223 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55223?
A fix for CVE-2026-55223 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55223 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55223

Explore →

Is Your Infrastructure Affected by CVE-2026-55223?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs