Skip to main content
VulnerabilityPublished

CVE-2026-42779: Apache MINA · Deserialization of Untrusted Data

Affects Apache MINASource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 9.8 Critical · fixed in 2.2.7 : patch Apache MINA as a priority.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.7, 2.1.12, 2.1.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade org.apache.mina/mina-core to 2.2.7, 2.1.12 or 2.1.0.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache MINAAffected
  • >=2.2.X <=2.2.6
  • >=2.1.X <=2.1.11
Fixed in–
MavenApache Software Foundation/org.apache.mina:mina-corepkg:maven/Apache Software Foundation/org.apache.mina:mina-coreOther threatsAffected
  • >=2.2.X <=2.2.6
  • >=2.1.X <=2.1.11
Fixed in–
Mavenorg.apache.mina/mina-corepkg:maven/org.apache.mina/mina-coreOther threatsAffected
  • <2.1.0
  • >=2.1.0 <2.1.12
  • >=2.2.0 <2.2.7
Fixed in
  • 2.1.0
  • 2.1.12
  • 2.2.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Apache MINA versions 2.1.12 and 2.2.7, which apply the classname allowlist earlier in the deserialization process to prevent this vulnerability. Users of affected versions should upgrade to these fixed releases. No vendor advisory was provided in the input, but the description clearly states the fixed versions. Until upgraded, applications remain vulnerable. There is no indication that this is a cloud service or that the vendor manages remediation server-side.

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.

References

Community reviews

Loading reviews…