dbcve.org
MinaApplication · Apache

CVE-2026-47065

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Two Java deserialization vulnerabilities in ObjectInputStream: (1) resolveProxyClass not overridden allows Proxy class instantiation to bypass acceptMatchers filter via Class.forName with latestUserDefinedLoader, and (2) Class.forName with initialize=true in readClassDescriptor triggers static initializers of allow-listed classes before instance construction, enabling side-effects from <clinit> blocks.

MitigationBoth vulnerabilities have been addressed in the codebase. For existing deployments, verify the fix is properly applied and conduct regression testing to ensure the deserialization allow-list functions as intended without triggering unintended class initializers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MinaApplication
Affected:= 2.0.29= 2.1.13= 2.2.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Mina installation
    Search for Mina JAR files (e.g., mina-core-*.jar) or Maven/Gradle dependencies containing 'org.apache.mina' in your classpath, application directory, or deployed libraries
    Affected if Apache Mina version 2.0.29, 2.1.13, or 2.2.8 is found in the environment
  2. Check application for Java deserialization
    Search codebase for ObjectInputStream usage or any custom deserialization logic that processes Java objects from untrusted sources, particularly in code that integrates with Apache Mina
    Affected if ObjectInputStream or custom deserialization handlers are used to process external data through Mina
  3. Inspect custom ObjectDeserializer implementations
    Review any custom ObjectInputStream subclass or ObjectDeserializer implementations that handle TC_PROXYCLASSDESC or readClassDescriptor calls in Mina-based communication
    Affected if Custom deserialization code exists that does not override resolveProxyClass() or readClassDescriptor() to validate against acceptMatchers allow-lists
  4. Verify deserialization filter configuration
    Examine if ObjectInputFilter or similar JVM-level deserialization filters are configured, and whether they explicitly validate proxy classes and class descriptors
    Affected if No custom filter validation exists for proxy classes and class descriptors, or filters rely solely on Mina's default behavior

You are affected if Apache Mina versions 2.0.29, 2.1.13, or 2.2.8 are in use and your application deserializes Java objects from untrusted sources without custom resolveProxyClass and readClassDescriptor validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Both vulnerabilities have been addressed in the codebase. For existing deployments, verify the fix is properly applied and conduct regression testing to ensure the deserialization allow-list functions as intended without triggering unintended class initializers.

Fix this in Mina Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47065 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data