CVE-2026-47065: Apache MINA · Deserialization of Untrusted Data
Affects Apache MINASource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in 2.2.8 : patch Apache MINA as a priority.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.2.8, 2.1.13, 2.0.29
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Apache to 2.2.8, 2.1.13 or 2.0.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache MINA | Affected
| Fixed in
|
| Apache Software FoundationApache MINA | Affected
| Fixed in
|
| Apache Software FoundationApache MINA | Affected
| Fixed in
|
MavenApache Software Foundation/org.apache.mina:mina-corepkg:maven/Apache Software Foundation/org.apache.mina:mina-coreOther threats | Affected
| Fixed in
|
Mavenorg.apache.mina/mina-corepkg:maven/org.apache.mina/mina-coreOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor has fully addressed these issues. However, no explicit patch or official fix version is provided in the available data. Users should consult the Apache Software Foundation advisories or official Apache MINA project communications for the latest patch or update information and apply any available updates promptly. Until then, consider restricting deserialization of untrusted data and monitoring for suspicious activity related to deserialization.
Description
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.