dbcve.org
MinaApplication · Apache

CVE-2026-41635

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to 2.0.28 / 2.1.11 or later.
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
Apache MINA's AbstractIoBuffer.resolveClass() contains two branches, one of them (for static classes or primitive types) does not check the class at all, bypassing the classname allowlist and allowing arbitrary code to be executed. The fix checks if the class is present in the accepted class filter before calling Class.forName().  Affected versions are Apache MINA 2.0.0 <= 2.0.27, 2.1.0 <= 2.1.10, and 2.2.0 <= 2.2.5. The problem is resolved in Apache MINA 2.0.28, 2.1.11, and 2.2.6 by applying the classname allowlist earlier. Affected are applications using Apache MINA that call  IoBuffer.getObject(). Applications using Apache MINA are advised to upgrade.

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

Apache MINA's AbstractIoBuffer.resolveClass() has a deserialization flaw where the branch handling static classes and primitive types bypasses the classname allowlist entirely, enabling arbitrary code execution via Class.forName() without validation. An attacker can exploit IoBuffer.getObject() to deserialize malicious objects.

MitigationUpgrade Apache MINA to version 2.0.28, 2.1.11, or 2.2.6 (or later) to apply the classname allowlist check before Class.forName() is called.

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.0, < 2.0.28>= 2.1.0, < 2.1.11>= 2.2.0, < 2.2.6

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 version
    Check the mina-core.jar manifest, or inspect pom.xml/gradle build files for the mina-core dependency version, or run: jar -xf mina-core.jar META-INF/MANIFEST.MF && cat META-INF/MANIFEST.MF
    Affected if The version falls within < 2.0.28, >= 2.0.0; or < 2.1.11, >= 2.1.0; or < 2.2.6, >= 2.2.0
  2. Locate IoBuffer.getObject() usage
    Search source code for calls to IoBuffer.getObject() or AbstractIoBuffer.getObject() method invocations, or grep -r 'getObject' across the codebase
    Affected if The application calls getObject() on IoBuffer instances to deserialize Java objects
  3. Determine data source trustworthiness
    Trace the source of data passed to IoBuffer.wrap() or IoBuffer.flip() before getObject() is called; check if it originates from network sockets, uploaded files, or other untrusted external inputs
    Affected if The deserialized data originates from untrusted or attacker-controlled sources such as network connections or user uploads
  4. Verify allowlist configuration (if any)
    Search for any custom ObjectInputStream subclass, ClassResolver configuration, or allowlist implementation that may have been added around the getObject() call
    Affected if No custom classname allowlist or validation is implemented before the getObject() call, and the code relies on the default MINA deserialization

You are affected if your Apache MINA version is below the fixed releases AND your application uses IoBuffer.getObject() to deserialize objects from untrusted sources without any custom allowlist 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.

dbcve · scoped
Upgrade available Upgrade to 2.0.28 / 2.1.11 / 2.2.6 or later
Fixed in 2.0.282.1.112.2.6
Interim mitigation

Upgrade Apache MINA to version 2.0.28, 2.1.11, or 2.2.6 (or later) to apply the classname allowlist check before Class.forName() is called.

Recommended fix High confidence

Apache MINA 2.0.28, 2.1.11, or 2.2.6 (depending on current version branch)

  1. Identify the current Apache MINA version in use by checking project dependencies (Maven pom.xml, Gradle build.gradle, or JAR manifest)
  2. Determine which version branch is currently in use (2.0.x, 2.1.x, or 2.2.x)
  3. Upgrade to the fixed version for that branch: 2.0.28 if on 2.0.x, 2.1.11 if on 2.1.x, or 2.2.6 if on 2.2.x
  4. Update the dependency in build configuration (Maven: <version>org.apache.mina:mina-core:VERSION</version> or Gradle: implementation 'org.apache.mina:mina-core:VERSION')
  5. Rebuild and redeploy the application
  6. Verify the application functions correctly after upgrade
Caveat Minor: Review release notes for any behavioral changes between versions; upgrades within same minor version typically have low risk

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mina Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41635 — 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-41635 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