Apache MINA Deserialization RCE Vulnerability

Exploitation

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

CVSS 4.0

10.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H · score source

EPSS

• CVE-2024-52046: 24.37% estimated exploitation activity in the next 30 days; percentile 97.87 (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.

The ObjectSerializationDecoder in Apache MINA uses Java’s native deserialization protocol to process incoming serialized data but lacks the necessary security checks and defenses. This vulnerability allows attackers to exploit the deserialization process by sending specially crafted malicious serialized data, potentially leading to remote code execution (RCE) attacks. This issue affects MINA core versions 2.0.X, 2.1.X and 2.2.X, and will be fixed by the releases 2.0.27, 2.1.10 and 2.2.4. It's also important to note that an application using MINA core library will only be affected if the IoBuffer#getObject() method is called, and this specific method is potentially called when adding a ProtocolCodecFilter instance using the ObjectSerializationCodecFactory class in the filter chain. If your application is specifically using those classes, you have to upgrade to the latest version of MINA core library. Upgrading will not be enough: you also need to explicitly allow the classes the…

Published by the source

25 Dec 2024, 12:30 UTC

Last modified by the source

11 Feb 2025, 19:03 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-76h9-2vwh-w278

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

# Patch Next advisory brief: CVE-2024-52046

Advisory: Apache MINA Deserialization RCE Vulnerability
IDs: CVE-2024-52046, GHSA-76h9-2vwh-w278
Record: https://patchnext.com/advisories/cve-2024-52046 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
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.4, 2.1.10, 2.0.27. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.mina:mina-core: affected >= 2.2.0, < 2.2.4; >= 2.1.0, < 2.1.10; >= 2.0.0-M1, < 2.0.27; fixed in 2.2.4, 2.0.27, 2.1.10

## 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-76h9-2vwh-w278 (GitHub-reviewed advisory GHSA-76h9-2vwh-w278 lists affected ranges: Maven org.apache.mina:mina-core >=2.2.0 =2.1.0 =2.0.0-M1 <2.0.27)

Commands are suggestions: review each one before running it.