Apache MINA: Critical Deserialization Allow-list Bypass via resolveProxyClass
Published 3 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected org.apache.mina:mina-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.2.0 <2.2.8
- Fixed in
- 2.2.8
mvn versions:use-dep-version -Dincludes=org.apache.mina:mina-core -DdepVersion=2.2.8 -DforceVersion=true- Affected
- >=2.1.0 <2.1.13
- Fixed in
- 2.1.13
mvn versions:use-dep-version -Dincludes=org.apache.mina:mina-core -DdepVersion=2.1.13 -DforceVersion=true- Affected
- <2.0.29
- Fixed in
- 2.0.29
mvn versions:use-dep-version -Dincludes=org.apache.mina:mina-core -DdepVersion=2.0.29 -DforceVersion=trueDetails
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.
Is GHSA-v3pr-hxpr-mfm8 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.mina:mina-core, and gives you the command that fixes it.
More advisories for org.apache.mina:mina-core
- CriticalCVE-2026-42778Apache MINA vulnerable to Deserialization of Untrusted Data (CVE-2026-41409 Incomplete Fix) · 1 May 2026
- CriticalCVE-2026-42779Apache MINA vulnerable to Deserialization of Untrusted Data (CVE-2026-41635 Incomplete Fix) · 1 May 2026
- CriticalCVE-2026-41409Apache MINA Vulnerable to Deserialization of Untrusted Data (CVE-2024-52046 Incomplete Fix) · 27 Apr 2026
- CriticalCVE-2026-41635Apache MINA vulnerable to Deserialization of Untrusted Data · 27 Apr 2026
- CriticalCVE-2024-52046Apache MINA Deserialization RCE Vulnerability · 25 Dec 2024
- HighCVE-2019-0231Cleartext Transmission of Sensitive Information in Apache MINA · 24 May 2022
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.