Apache MINA vulnerable to Deserialization of Untrusted Data

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-41635: 0.62% estimated exploitation activity in the next 30 days; percentile 49.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

27 Apr 2026, 09:34 UTC

Last modified by the source

7 May 2026, 05:27 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8297-v2rf-2p32

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41635

Advisory: Apache MINA vulnerable to Deserialization of Untrusted Data
IDs: CVE-2026-41635, GHSA-8297-v2rf-2p32
Record: https://patchnext.com/advisories/cve-2026-41635 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.mina:mina-core 2.2.6, 2.1.11, 2.0.28. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.mina:mina-core: affected >= 2.0.0, < 2.0.28; >= 2.1.0, < 2.1.11; >= 2.2.0, < 2.2.6; fixed in 2.2.6, 2.1.11, 2.0.28

## Suggested inspection (read-only)
- Maven org.apache.mina:mina-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.mina:mina-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8297-v2rf-2p32 (GitHub-reviewed advisory GHSA-8297-v2rf-2p32 lists affected ranges: Maven org.apache.mina:mina-core >=2.0.0 =2.1.0 =2.2.0 <2.2.6)

Commands are suggestions: review each one before running it.