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 46% 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%CVSS: 9.8Exploit: Elevated riskExposed: 0

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.8(medium)
EG Risk
60(Track*)
EG Risk 60/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
Severity98% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

February 25, 2026

Last Modified

August 17, 2026

Advisory Details (11)

Auto-updated Aug 24, 2026
Patch available. Sources: github, redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:34365
redhat Patch Available

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
redhat Patch Available

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
redhat Patch Available

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
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:14874
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:14873
generic

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

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

c3p0-v0.14.1 - 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
github Patch Available

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
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3890

Vendor Advisories for CVE-2026-27727(8)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
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
redhatmchange-commons-java2026-05-18redhat
redhatcandlepin-0:4.4.25-1.el9sat2026-05-07redhat

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 rangeFixed inDependents
com.mchange:mchange-commons-java0.2.1-RELEASE ... 0.3.2 (31 versions)0.4.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 65× 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 115 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 in the National Vulnerability Database on February 25, 2026, with the most recent update on August 17, 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% probability of exploitation in the next 30 days, which ranks it in the top 45.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27727, 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-27727

Explore →

Is Your Infrastructure Affected by CVE-2026-27727?

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

Start Free Scan →Browse All CVEs