CVE-2026-27727

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 45% 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, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.6%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

mchange-commons-java, a library that provides Java utilities, includes code that mirrors early implementations of JNDI functionality, including support for remote factoryClassLocation values, by which code can be downloaded and invoked within a running application. If an attacker can provoke an application to read a maliciously crafted jaxax.naming.Reference or serialized object, they can provoke the download and execution of malicious code. Implementations of this functionality within the JDK were disabled by default behind a System property that defaults to false, com.sun.jndi.ldap.object.trustURLCodebase. However, since mchange-commons-java includes an independent implementation of JNDI derefencing, libraries (such as c3p0) that resolve references via that implementation could be provoked to download and execute malicious code even after the JDK was hardened. Mirroring the JDK patch, mchange-commons-java's JNDI functionality is gated by configuration parameters that default to restrictive values starting in version 0.4.0. No known workarounds are available. Versions prior to 0.4.0 should be avoided on application CLASSPATHs.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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
Severity98% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
1.6%
EPSS %ILE
74th
KEV
Not listed

Published

February 25, 2026

Last Modified

September 15, 2026

Advisory Details (11)

Auto-updated Oct 6, 2026
Patch available. Sources: github.
generic

c3p0-v0.14.2 - JDBC3 Connection and Statement Pooling - Documentation

https://www.mchange.com/projects/c3p0/#security-note
generic

c3p0-v0.14.2 - JDBC3 Connection and Statement Pooling - Documentation

https://www.mchange.com/projects/c3p0/#configuring_security
generic

c3p0, you little rascal | MOGWAI LABS

https://mogwailabs.de/en/blog/2025/02/c3p0-you-little-rascal
githubMentions a patch (unverified)

mchange-commons-java prior to v0.4.0 can be dangerously abused to download and execute malicious code · Advisory · swaldman/mchange-commons-java · GitHub

https://github.com/swaldman/mchange-commons-java/security/advisories/GHSA-m2cm-222f-qw44
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:34365
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:18059
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:18055
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:18054
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:14874
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:14873
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:3890

Vendor Advisories for CVE-2026-27727(10)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibc3p0-java-doc (0.9.1.2-9+deb8u1ubuntu0.18.04.1+esm1) @ bionic2026-09-15ubuntu
redhatcandlepin-0:4.7.5-1.el9sat2026-07-01redhat
redhateap8-hibernate-0:6.6.48-1.Final_redhat_00001.1.el8eap2026-05-18redhat
redhateap8-hibernate-0:6.6.48-1.Final_redhat_00001.1.el9eap2026-05-18redhat
redhatorg.hibernate.orm/hibernate-core:6.6.48.Final-redhat-000012026-05-18redhat
redhatcandlepin-0:4.4.25-1.el9sat2026-05-07redhat
redhatmchange-commons-java2026-03-11redhat

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.3.2 (31 versions)
  • every version up to 0.4.0: fixed in 0.4.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 / 25× 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 155 total refreshes for this CVE.

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

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-27727?
CVE-2026-27727 is a critical vulnerability published on February 25, 2026. mchange-commons-java, a library that provides Java utilities, includes code that mirrors early implementations of JNDI functionality, including support for remote factoryClassLocation values, by which code can be downloaded and invoked within a running application. If an attacker can provoke an…
When was CVE-2026-27727 disclosed?
CVE-2026-27727 was first published on February 25, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27727 actively exploited?
CVE-2026-27727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27727?
CVE-2026-27727 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-27727?
A fix for CVE-2026-27727 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-27727 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-27727

Explore →

Is Your Infrastructure Affected by CVE-2026-27727?

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

Book a Demo →Browse All CVEs