CVE-2026-41409

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

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2026-41409 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.28, 2.1.11, 2.2.6); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-41409? CVE-2026-41409 is a critical-severity insecure deserialization vulnerability in org.apache.mina:mina-core (maven), affecting versions >= 2.0.0, < 2.0.28. It is fixed in 2.0.28, 2.1.11, 2.2.6. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2026-41409? CVE-2026-41409 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.mina:mina-core are affected by CVE-2026-41409? org.apache.mina:mina-core (maven) versions >= 2.0.0, < 2.0.28 is affected.
4. Is there a fix for CVE-2026-41409? Yes. CVE-2026-41409 is fixed in 2.0.28, 2.1.11, 2.2.6. Upgrade to this version or later.
5. Is CVE-2026-41409 exploitable, and should I be worried? Whether CVE-2026-41409 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41409 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41409?
   • Upgrade org.apache.mina:mina-core to 2.0.28 or later
   • Upgrade org.apache.mina:mina-core to 2.1.11 or later
   • Upgrade org.apache.mina:mina-core to 2.2.6 or later