CVE-2026-55153

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

mchange-commons-java is a Java library of shared utility classes used by mchange projects like the c3p0 connection pool. Prior to version 0.6.0, its JNDI ObjectFactory implementation (com.mchange.v2.naming.JavaBeanObjectFactory) will construct objects of arbitrary classes and initialize "JavaBean"-style properties, which for certain classes enables JNDI injection and "deserialization gadgets." Such initialization is unsafe for some classes: for example, setting the contentType property of a Swing JEditorPane to text/html and its text property to HTML containing a stylesheet will provoke an HTTP GET on an arbitrary URL, potentially from within a trusted security domain. The problem is aggravated by the library's ReferenceIndirector, through which malicious JNDI Reference objects can be smuggled in for dereferencing wherever an application reads a Java-serialized object. This has been resolved in version 0.6.0.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

Published

July 1, 2026

Last Modified

July 6, 2026

Advisory Details (1)

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

mchange-commons-java prior to v0.6.0 contains elements susceptible to abuse via JNDI injection and "deserialization gadgets". · Advisory · swaldman/mchange-commons-java · GitHub

https://github.com/swaldman/mchange-commons-java/security/advisories/GHSA-h84g-69h7-mw6v

Vendor Advisories for CVE-2026-55153(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
redhatmchange-commons-java2026-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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.mchange:mchange-commons-java0.2.1-RELEASE ... 0.5.0 (33 versions)
  • every version up to 0.6.0: fixed in 0.6.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 / 35× 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 170 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 06:48 UTCEG score recompute
  18. 2026-09-23 06:48 UTCVendor advisory
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 06:28 UTCEG score recompute
  22. 2026-09-18 06:28 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-14 00:21 UTCEG score recompute
  3. 2026-09-14 00:21 UTCVendor advisory
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 09:07 UTCEG score recompute
  6. 2026-09-13 09:07 UTCVendor advisory
  7. 2026-09-12 14:36 UTCEG score recompute
  8. 2026-09-12 14:36 UTCVendor advisory
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 14:26 UTCEG score recompute
  14. 2026-09-06 14:26 UTCVendor advisory
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-06 00:37 UTCEG score recompute
  17. 2026-09-06 00:37 UTCVendor advisory
  18. 2026-09-04 05:06 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-08-30 23:28 UTCEG score recompute
  22. 2026-08-30 23:28 UTCVendor advisory
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 11:42 UTCEG score recompute
  25. 2026-08-30 11:42 UTCVendor advisory
  26. 2026-08-30 01:22 UTCEPSS rescore
  27. 2026-08-28 21:41 UTCEPSS rescore
  28. 2026-08-27 22:24 UTCEG score recompute
  29. 2026-08-27 22:24 UTCVendor advisory
  30. 2026-08-27 14:25 UTCEPSS rescore
  31. 2026-08-26 14:46 UTCEPSS rescore
  32. 2026-08-25 16:16 UTCEG score recompute
  33. 2026-08-25 16:16 UTCVendor advisory
  34. 2026-08-25 13:49 UTCEPSS rescore
  35. 2026-08-24 20:58 UTCEG score recompute
  36. 2026-08-24 20:58 UTCVendor advisory
  37. 2026-08-24 06:36 UTCVendor advisory
  38. 2026-08-23 19:03 UTCVendor advisory
  39. 2026-08-23 07:28 UTCEG score recompute
  40. 2026-08-23 07:28 UTCVendor advisory
  41. 2026-08-23 00:19 UTCEPSS rescore
  42. 2026-08-22 19:53 UTCVendor advisory
  43. 2026-08-22 06:55 UTCEG score recompute
  44. 2026-08-22 06:55 UTCVendor advisory
  45. 2026-08-21 23:49 UTCEPSS rescore
  46. 2026-08-21 17:16 UTCVendor advisory
  47. 2026-08-21 04:30 UTCEG score recompute
  48. 2026-08-21 04:30 UTCVendor advisory
  49. 2026-08-20 22:55 UTCEPSS rescore
  50. 2026-08-20 16:13 UTCVendor advisory
  51. 2026-08-20 04:36 UTCEG score recompute
  52. 2026-08-20 04:36 UTCVendor advisory
  53. 2026-08-19 17:04 UTCEPSS rescore
  54. 2026-08-19 11:25 UTCVendor advisory
  55. 2026-08-18 23:35 UTCEG score recompute
  56. 2026-08-18 23:35 UTCVendor advisory
  57. 2026-08-18 13:48 UTCEPSS rescore
  58. 2026-08-18 11:57 UTCVendor advisory
  59. 2026-08-17 23:18 UTCEG score recompute
  60. 2026-08-17 23:18 UTCVendor advisory
  61. 2026-08-17 13:47 UTCEPSS rescore
  62. 2026-08-17 08:45 UTCVendor advisory
  63. 2026-08-16 21:12 UTCEG score recompute
  64. 2026-08-16 21:12 UTCVendor advisory
  65. 2026-08-16 14:56 UTCEPSS rescore
  66. 2026-08-16 09:38 UTCEG score recompute
  67. 2026-08-16 09:38 UTCVendor advisory
  68. 2026-08-16 02:14 UTCEPSS rescore
  69. 2026-08-15 22:05 UTCVendor advisory
  70. 2026-08-15 10:31 UTCEG score recompute
  71. 2026-08-15 10:31 UTCVendor advisory
  72. 2026-08-15 01:30 UTCEPSS rescore
  73. 2026-08-14 22:57 UTCVendor advisory
  74. 2026-08-14 11:23 UTCVendor advisory
  75. 2026-08-13 23:50 UTCEG score recompute

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

Same product

1 shown

Maven:com.mchange:mchange-commons-java

Frequently asked(5)

What is CVE-2026-55153?
CVE-2026-55153 is a high vulnerability published on July 1, 2026. mchange-commons-java is a Java library of shared utility classes used by mchange projects like the c3p0 connection pool. Prior to version 0.6.0, its JNDI ObjectFactory implementation (com.mchange.v2.naming.JavaBeanObjectFactory) will construct objects of arbitrary classes and initialize…
When was CVE-2026-55153 disclosed?
CVE-2026-55153 was first published on July 1, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55153 actively exploited?
CVE-2026-55153 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55153?
CVE-2026-55153 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55153?
A fix for CVE-2026-55153 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55153 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-55153

Explore →

Is Your Infrastructure Affected by CVE-2026-55153?

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

Book a Demo →Browse All CVEs