CVE-2026-27727
RCE via remote JNDI dereferencing in mchange-commons-java
Is CVE-2026-27727 being exploited?
Not confirmed. CVE-2026-27727 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.81% probability of exploitation in the next 30 days.
How severe is CVE-2026-27727?
CVE-2026-27727 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-27727?
Yes. A fix has been recorded for CVE-2026-27727. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-27727 affect?
CVE-2026-27727 affects Java applications using mchange-commons-java JNDI functionality (e.g., via c3p0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-27727?
Upgrade to 0.4.0+ or remove JNDI usage
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via crafted remote JNDI references; attacker can load and execute code in app process
Patch when possible
- affected< 0.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.