CVE-2026-41409

Apache MINA: CWE-502 Deserialization of Untrusted Data

Published Apr 27, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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.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

Analysis

AI-generated

Technical impact

The vulnerability lies in Apache MINA's AbstractIoBuffer.getObject() method. Because the classname allowlist is applied only after a static initializer has already been executed, an attacker can send crafted serialized data that triggers arbitrary code execution during deserialization. This weakness is a classic deserialization flaw (CWE‑502) that can compromise confidentiality, integrity, and availability of any system using the affected MINA framework.

Affected Systems

The issue affects Apache MINA versions 2.0.0 through 2.0.27, 2.1.0 through 2.1.10, and 2.2.0 through 2.2.5. Applications or services that incorporate Apache MINA and invoke IoBuffer.getObject() are vulnerable.

Risk and Exploitability

Based on the description, the likely attack vector is remote, originating from network traffic that passes through services using MINA's deserialization. With a CVSS score of 9.8, this vulnerability is considered critical. The EPSS score of <1% indicates that, at present, the likelihood of exploitation is low but non-zero. It is not listed in the CISA KEV catalog. The vulnerability therefore carries a high severity and a small but present exploitation probability.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache MINA to version 2.0.28, 2.1.11, or 2.2.6 or later, which applies the classname allowlist at the correct time.
  • Configure the application to restrict deserialization to a strict whitelist of trusted classes and disallow any payloads from untrusted external sources.
  • Implement network segmentation and logging for all traffic reaching the MINA endpoints, and monitor for anomalous deserialization activity.

Generated by OpenCVE AI on April 28, 2026 at 04:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-f2wh-grmh-r6jm Apache MINA Vulnerable to Deserialization of Untrusted Data (CVE-2024-52046 Incomplete Fix)
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:mina:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Apache
Apache mina
Vendors & Products Apache
Apache mina
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.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
Title Apache MINA: CWE-502 Deserialization of Untrusted Data
Weaknesses CWE-502
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Apr 27, 2026, 12:21 PM
Reserved
Apr 20, 2026, 3:04 PM
Status
Analyzed
Published
Apr 27, 2026, 10:16 AM
Modified
Oct 26, 2026, 9:10 PM
Severity
Critical
Public date
Apr 27, 2026, 9:20 AM