CVE-2026-27727: mchange-commons-java: Remote Code Execution via JNDI Reference Resolution
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.97% (FIRST EPSS); higher than 62.4% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: com.mchange:mchange-commons-java (Maven) 0.4.0; c3p0 (openSUSE:Leap 15.6) 0.9.5.5-150400.3.5.1; mchange-commons (openSUSE:Leap 15.6) 0.2.20-150400.3.3.1.
Low priority for now. Upgrade to com.mchange:mchange-commons-java (Maven) 0.4.0; c3p0 (openSUSE:Leap 15.6) 0.9.5.5-150400.3.5.1; mchange-commons (openSUSE:Leap 15.6) 0.2.20-150400.3.3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 25, 2026
- Updated
- Sep 15, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-74
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mchange | mchange commons java | cpe:2.3:a:mchange:mchange_commons_java |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mchange mchange commons javabefore 0.4.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
swaldman mchange-commons-java
- < 0.4.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | com.mchange:mchange-commons-java | before 0.4.0 | 0.4.0 |
| openSUSE:Leap 15.6 | c3p0 | before 0.9.5.5-150400.3.5.1 | 0.9.5.5-150400.3.5.1 |
| openSUSE:Leap 15.6 | mchange-commons | before 0.2.20-150400.3.3.1 | 0.2.20-150400.3.3.1 |
| openSUSE:Tumbleweed | c3p0 | before 0.12.0-1.1 | 0.12.0-1.1 |
| openSUSE:Tumbleweed | mchange-commons | before 0.4.0-1.1 | 0.4.0-1.1 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-hibernate | before 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 | 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-hibernate-core | before 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 | 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-hibernate-entitymanager | before 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 | 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-hibernate-envers | before 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 | 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-hibernate-infinispan | before 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 | 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-hibernate-java8 | before 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 | 0:5.1.17-5.Final_redhat_00006.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-netty | before 0:4.1.63-4.Final_redhat_00005.1.ep7.el7 | 0:4.1.63-4.Final_redhat_00005.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-netty-all | before 0:4.1.63-4.Final_redhat_00005.1.ep7.el7 | 0:4.1.63-4.Final_redhat_00005.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-wildfly | before 0:7.1.16-1.GA_redhat_00002.1.ep7.el7 | 0:7.1.16-1.GA_redhat_00002.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.1::el7 | eap7-wildfly-modules | before 0:7.1.16-1.GA_redhat_00002.1.ep7.el7 | 0:7.1.16-1.GA_redhat_00002.1.ep7.el7 |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-hibernate | before 0:5.3.39-1.Final_redhat_00001.1.el7eap | 0:5.3.39-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-hibernate-core | before 0:5.3.39-1.Final_redhat_00001.1.el7eap | 0:5.3.39-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-hibernate-entitymanager | before 0:5.3.39-1.Final_redhat_00001.1.el7eap | 0:5.3.39-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-hibernate-envers | before 0:5.3.39-1.Final_redhat_00001.1.el7eap | 0:5.3.39-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-hibernate-java8 | before 0:5.3.39-1.Final_redhat_00001.1.el7eap | 0:5.3.39-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-jboss-server-migration | before 0:1.7.2-24.Final_redhat_00026.1.el7eap | 0:1.7.2-24.Final_redhat_00026.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-jboss-server-migration-cli | before 0:1.7.2-24.Final_redhat_00026.1.el7eap | 0:1.7.2-24.Final_redhat_00026.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-jboss-server-migration-core | before 0:1.7.2-24.Final_redhat_00026.1.el7eap | 0:1.7.2-24.Final_redhat_00026.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-jboss-server-migration-eap6.4 | before 0:1.7.2-24.Final_redhat_00026.1.el7eap | 0:1.7.2-24.Final_redhat_00026.1.el7eap |
+96
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:com.mchange:mchange-commons-java | 0.4.0 | Package registry (OSV) |
| opensuse:c3p0 | 0.9.5.5-150400.3.5.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:mchange-commons | 0.2.20-150400.3.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:candlepin | 0:4.4.25-1.el9sat · Red Hat:satellite:6.17::el9 | Package registry (OSV) |
| red hat:candlepin-selinux | 0:4.4.25-1.el9sat · Red Hat:satellite:6.17::el9 | Package registry (OSV) |
| red hat:eap8-bouncycastle | 0:1.84.0-1.redhat_00001.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.1::el8 | Package registry (OSV) |
| red hat:python-markdown | 0:3.8.2-1.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:python-pillow | 0:12.1.1-1.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:python-pillow-debugsource | 0:12.1.1-1.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:python-pyOpenSSL | 0:25.1.0-0.3.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:python3.11-markdown | 0:3.8.2-1.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:python3.11-pillow | 0:12.1.1-1.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:python3.11-pillow-debuginfo | 0:12.1.1-1.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:python3.11-pyOpenSSL | 0:25.1.0-0.3.el9pc · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
| red hat:rubygem-activesupport | 0:7.0.8.7-2.el9sat · Red Hat:satellite_capsule:6.17::el9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- HTTP Request SplittingCAPEC-105likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Format String InjectionCAPEC-135likelihood: High · High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (13 more)Show less
- www.mchange.com/projects/c3p0/#configuring_security
- www.mchange.com/projects/c3p0/#security-note
- access.redhat.com/errata/RHSA-2026:14873
- access.redhat.com/errata/RHSA-2026:14874
- access.redhat.com/errata/RHSA-2026:18054
- access.redhat.com/errata/RHSA-2026:18055
- access.redhat.com/errata/RHSA-2026:18059
- access.redhat.com/errata/RHSA-2026:34365
- access.redhat.com/errata/RHSA-2026:3890
- access.redhat.com/errata/RHSA-2026:4285
- access.redhat.com/security/cve/CVE-2026-27727
- bugzilla.redhat.com/show_bug.cgi?id=2442671
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-27727.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.