CVE-2026-47065
Apache MINA: Critical Deserialization Allow-list Bypass via resolveProxyClass - ZDRES-232
Reported by apache · Published June 3, 2026
mina-core is fixed in 2.2.8, 2.1.13 and 2.0.29 (Maven Central)
ZDRES-232: resolveProxyClass Not Overridden - acceptMatchers Filter Bypass via java.lang.reflect.Proxy Assessment: Fully addressed. When the serialised stream contains a TC_PROXYCLASSDESC (the marker for a java.lang.reflect.Proxy ), JDK’s ObjectInputStream.readProxyDesc() is dispatched. JDK then calls the default ObjectInputStream.resolveProxyClass(interfaces) implementation, which performs Class.forName(intf, false, latestUserDefinedLoader()) for EACH interface name and constructs the proxy class — bypassing the accepted classes list . ZDRES-233: Class.forName(name, initialize=true, classLoader) in readClassDescriptor Triggers Static Initialiser of Allow-Listed Classes Assessment: Fully addressed. For ANY class on the allow-list, deserialising a stream that names it triggers the class’s (static initialiser) BEFORE any instance is constructed. This means an attacker who supplies a class name on the allow-list (e.g., the developer wrote accept(“com.myapp.*") , attacker supplies com.myapp.SomeClass ) causes <clinit> of SomeClass — and many real-world classes have side-effecting static initialisers Both issues have been fixed.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| org.apache.mina:mina-core | Maven Central | 2.2.8, 2.1.13, 2.0.29 |
| hadoop-fips-3.5 | Chainguard | 3.5.0-r2 |
| apache-nifi | Wolfi | 2.10.0-r4 |
| apache-nifi | Chainguard | 2.10.0-r4 |
| jenkins-2 | Wolfi | 2.577-r0 |
| jenkins-2.568 | Chainguard | 2.568.1-r2 |
| guacamole-client | Chainguard | 1.6.0-r13 |
| jenkins-2 | Chainguard | 2.577-r0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache MINA | 2.2.0, 2.1.0, 2.0.0 |
| chainguard | hadoop-fips-3.5 | 0 |
| wolfi | apache-nifi | 0 |
| Apache Software Foundation | Apache MINA | 2.0.0, 2.2.0, 2.1.0 |
| chainguard | apache-nifi | 0 |
| wolfi | jenkins-2 | 0 |
| chainguard | jenkins-2.568 | 0 |
| chainguard | guacamole-client | 0 |
| chainguard | jenkins-2 | 0 |
| Maven | org.apache.mina:mina-core | 2.2.0, 2.1.0, 0 |
Timeline
- Jun 3, 2026 CVE Published
- Jun 4, 2026 Coalition ESS Score
- Jun 4, 2026 CVE Updated
- Jun 5, 2026 EPSS Score (30 in total, the first dated here)
- Jun 7, 2026 Security Advisory
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-47065
vulnetix vdb fixes CVE-2026-47065
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-47065/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- vendor-advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-47065 advisory
- https://github.com/advisories/GHSA-v3pr-hxpr-mfm8 advisory