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.5%, top 61% 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
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

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.3(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
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.
github Patch Available

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 / EcosystemFixed in / PatchReleasedSource
ubuntulibc3p0-java-doc (0.9.1.2-10ubuntu0.20.04.1+esm1) @ focal2026-08-25ubuntu
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 rangeFixed inDependents
c3p00.9.1.2-10, 0.9.1.2-10.1, 0.9.1.2-10.1~deb12u1, 0.9.1.2-11——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
c3p00.9.1.2-10, 0.9.1.2-10.1, 0.9.1.2-10.1~deb12u1, 0.9.1.2-11——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
c3p00.9.1.2-10.1, 0.9.1.2-11——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
c3p00.9.1.2-10.1, 0.9.1.2-11——
Maven(1)
PackageVulnerable rangeFixed inDependents
com.mchange:c3p00.10.0 ... 0.9.5.5 (42 versions)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 16× in last 7d / 62× 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 103 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 60.7% of all scored CVEs.
What is the CVSS score of CVE-2026-55223?
CVE-2026-55223 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-55223?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55223, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs