CVE-2026-42779 Apache MINA vulnerable to Deserialization of Untrusted Data (CVE-2026-41635 Incomplete Fix)

Critical 9.8 Published Updated

Attackers can execute arbitrary code via unsafe deserialization in Apache MINA when applications call IoBuffer.getObject(), bypassing class filters.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-42779?

CVE-2026-42779 is a critical unsafe deserialization vulnerability in Apache MINA, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

The fix for CVE-2026-41635 was not applied to the 2.1.X and 2.2.X branches. Here was the original issue description:

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.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.

Weakness: CWE-502

Which versions are affected by CVE-2026-42779?

4 open source packages ship an affected version, including org.apache.mina:mina-core. It affects 1 product.

PackageAffectedFixed in
org.apache.mina:mina-core MavenFrom 2.1.02.1.12
org.apache.mina:mina-core MavenFrom 2.1.02.1.12
org.apache.mina:mina-core MavenFrom 2.2.02.2.7
org.apache.mina:mina-core MavenFrom 2.2.02.2.7

Products include Apache Mina.

How do I fix CVE-2026-42779?

Upgrade org.apache.mina:mina-core to a fixed version for your release line: 2.1.12 or 2.2.7.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2026-42779 being exploited?

There is no known exploitation of CVE-2026-42779 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as CLEANSTART-2026-BL56844, CLEANSTART-2026-BZ36628, CLEANSTART-2026-GX72554, CLEANSTART-2026-OA86138, CLEANSTART-2026-YJ76676, ECHO-5cd5-f8bb-3443 and 9 more.

Is CVE-2026-42779 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free