How severe is CVE-2026-27727?

No CVSS score has been assigned to CVE-2026-27727 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-27727?

CVE-2026-27727 affects the following packages: com.mchange:mchange-commons-java (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-27727?

Update com.mchange:mchange-commons-java to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27727 is resolved across your whole dependency graph.

How do I detect CVE-2026-27727 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.mchange:mchange-commons-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-27727 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-27727?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27727 can be triaged on real exposure rather than presence alone.

Is CVE-2026-27727 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-27727 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-27727?

CVE-2026-27727 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-27727?

CVE-2026-27727 is classified as CWE-74 (CWE-74), Deserialization of Untrusted Data (CWE-502). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-27727 published, and has it been updated?

CVE-2026-27727 was published on February 25, 2026 and was last updated on September 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2026-27727 — mchange-commons-java

CVE-2026-27727 is a CWE-74 vulnerability in com.mchange:mchange-commons-java. A fix is available for com.mchange:mchange-commons-java — see the affected versions and patch details below.

mchange-commons-java: Remote Code Execution via JNDI Reference Resolution

Also known asGHSA-m2cm-222f-qw44

Published

Feb 25, 2026

Updated

Sep 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27727.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕com.mchange:mchange-commons-java

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

mchange-commons-java 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.

Patches

Mirroring the JDK patch, mchange-commons-java's JNDI functionality is now gated by configuration parameters that default to restrictive values. Those parameters are documented here.

Workarounds

No. Users should upgrade to mchange-commons-java >= 0.4.0. Earlier versions should be avoided on application CLASSPATHs.

References

c3p0, you little rascal — Hans-Martin Münch c3p0 documentation, security note c3p0 documentation, configuring security

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.mchange:mchange-commons-java`	all versions	0.4.0`com.mchange:mchange-commons-java:0.4.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.mchange:mchange-commons-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.mchange:mchange-commons-java to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27727 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27727 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-27727. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat build of Apache Camel 4.14.4 for Spring Boot 3.5.11	`mchange-commons-java`	RHSA-2026:3890
Red Hat JBoss Enterprise Application Platform 8.1.7.GA	`org.hibernate.orm/hibernate-core:6.6.48.Final-redhat-00001`	RHSA-2026:18059
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8	`eap8-hibernate-0:6.6.48-1.Final_redhat_00001.1.el8eap`	RHSA-2026:18054
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9	`eap8-hibernate-0:6.6.48-1.Final_redhat_00001.1.el9eap`	RHSA-2026:18055
Red Hat Satellite 6.16 for RHEL 8	`candlepin-0:4.4.25-1.el8sat`	RHSA-2026:14874
Red Hat Satellite 6.17 for RHEL 9	`candlepin-0:4.4.25-1.el9sat`	RHSA-2026:14873
Red Hat Satellite 6.19 for RHEL 9	`candlepin-0:4.7.5-1.el9sat`	RHSA-2026:34365

UbuntuHIGH

USN-8642-1Ubuntu

Frequently Asked Questions

### Impact mchange-commons-java 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`. Howev

O3 Security · Impact-Aware SCA

Is CVE-2026-27727 in your dependencies?

O3 Security finds CVE-2026-27727 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CVE-2026-27727 — mchange-commons-java

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2026-27727 in your dependencies?