dbcve.org
MinaApplication · Apache

CVE-2026-42778

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-01
Fix available
A fix is available. Upgrade to 2.1.12 / 2.2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
The fix for CVE-2026-41409 was not applied to the 2.1.X and 2.2.X branches. Here was the original issue description: The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a static initializer in a class to be read might already have been executed. Affected versions are Apache MINA 2.1.0 <= 2.1.11, and 2.2.0 <= 2.2.6. The problem is resolved in Apache MINA 2.1.12, and 2.2.7 by applying the classname allowlist earlier. Affected are applications using Apache MINA that call IoBuffer.getObject(). Applications using Apache MINA are advised to upgrade The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a static initializer in a class to be read might already have been executed. Affected versions are Apache MINA 2.1.0 <= 2.1.110, and 2.2.0 <= 2.2.6. The problem is resolved in Apache MINA 2.1.12, and 2.2.7 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

Incomplete fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() allows deserialization attacks. The classname allowlist check is applied after static initializers in the target class may have already executed, potentially enabling arbitrary code execution. The vulnerability affects versions 2.1.0 through 2.1.11 and 2.2.0 through 2.2.6.

MitigationUpgrade to Apache MINA 2.1.12, 2.2.7, or later versions where the classname allowlist is applied earlier in the deserialization process.

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.1.0, < 2.1.12>= 2.2.0, < 2.2.7

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 dependency
    Search your project dependencies (Maven pom.xml, Gradle build.gradle, or JAR files in classpath) for 'mina-core' or 'apache-mina' and note the exact version number.
    Affected if The version is 2.1.0-2.1.11 or 2.2.0-2.2.6
  2. Locate MINA JAR file version
    If using bundled JARs, locate mina-core.jar in your application classpath and check the MANIFEST.MF file inside the JAR for the Implementation-Version attribute, or use 'java -jar mina-core.jar' if it has a main class to query version.
    Affected if The reported version falls within the affected ranges 2.1.0-2.1.11 or 2.2.0-2.2.6
  3. Check for AbstractIoBuffer.getObject() usage
    Search your codebase for calls to AbstractIoBuffer.getObject(), IoBuffer.getObject(), or equivalent buffer.getObject() where the buffer is from MINA, or inspect network traffic handlers that deserialize objects from incoming data.
    Affected if Your application deserializes objects via MINA buffer methods and uses a MINA version in the affected range
  4. Verify deserialization is enabled
    Examine your MINA IoHandler or codec configuration to confirm that object deserialization (such as using ObjectSerializationCodec or custom object decoding) is active and processing incoming data.
    Affected if Object deserialization is enabled and the MINA version is vulnerable

You are affected if your environment uses Apache MINA versions 2.1.0-2.1.11 or 2.2.0-2.2.6 and deserializes objects through AbstractIoBuffer.getObject() or equivalent MINA buffer methods.

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.1.12 / 2.2.7 or later
Fixed in 2.1.122.2.7
Vendor patch lists.apache.org →
Interim mitigation

Upgrade to Apache MINA 2.1.12, 2.2.7, or later versions where the classname allowlist is applied earlier in the deserialization process.

Recommended fix High confidence

Apache MINA 2.1.12 or 2.2.7

  1. Identify the current Apache MINA version in your project's dependency management (e.g., pom.xml, build.gradle, or package manager)
  2. Determine which version branch you are currently using (2.1.x or 2.2.x)
  3. Update the dependency version to the appropriate fixed release: 2.1.12 for 2.1.x branch, or 2.2.7 for 2.2.x branch
  4. If using Maven, update the version in pom.xml: change <version>2.1.X</version> to <version>2.1.12</version> or <version>2.2.X</version> to <version>2.2.7</version>
  5. If using Gradle, update the version in build.gradle: change 'org.apache.mina:mina-core:2.1.X' to 'org.apache.mina:mina-core:2.1.12' or '2.2.7'
  6. Rebuild the project and run all tests to ensure compatibility
  7. Verify the application works correctly with the new version before deploying to production

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

Fix this in Mina Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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