CVE-2024-52046: Apache MINA Deserialization RCE Vulnerability
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.
Published Dec 25, 2024 · Updated Feb 11, 2025
Affected packages
org.apache.mina:mina-core
- Ecosystem
- Maven
- Affected
- >= 2.2.0, < 2.2.4
- Fixed in
- 2.2.4
- Check
mvn dependency:tree -Dincludes=org.apache.mina:mina-core
org.apache.mina:mina-core
- Ecosystem
- Maven
- Affected
- >= 2.1.0, < 2.1.10
- Fixed in
- 2.1.10
- Check
mvn dependency:tree -Dincludes=org.apache.mina:mina-core
org.apache.mina:mina-core
- Ecosystem
- Maven
- Affected
- >= 2.0.0-M1, < 2.0.27
- Fixed in
- 2.0.27
- Check
mvn dependency:tree -Dincludes=org.apache.mina:mina-core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 decoder will accept in the ObjectSerializationDecoder instance, using one of the three new methods:
- Accept class names where the supplied ClassNameMatcher matches for deserialization, unless they are otherwise rejected.
@param classNameMatcherthe matcher to use- /
public void accept(ClassNameMatcher classNameMatcher)
- Accept class names that match the supplied pattern for deserialization, unless they are otherwise rejected.
@parampattern standard Java regexp- /
public void accept(Pattern pattern)
3.
- Accept the wildcard specified classes for deserialization, unless they are otherwise rejected.
@parampatterns Wildcard file name patterns as defined by{@link org.apache.commons.io.FilenameUtils#wildcardMatch(String, String) FilenameUtils.wildcardMatch}- /
public void accept(String... patterns)
By default, the decoder will reject *all* classes that will be present in the incoming data.
Note: The FtpServer, SSHd and Vysper sub-project are not affected by this issue.
Credited to Malayke.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Maven vulnerabilities
All Maven entriesCVE-2026-47065
Apache MINA: Critical Deserialization Allow-list Bypass via resolveProxyClass
critical9.8Jun 3, 2026CVE-2026-42778
Apache MINA vulnerable to Deserialization of Untrusted Data (CVE-2026-41409 Incomplete Fix)
critical9.8May 1, 2026CVE-2026-42779
Apache MINA vulnerable to Deserialization of Untrusted Data (CVE-2026-41635 Incomplete Fix)
critical9.8May 1, 2026CVE-2026-41409
Apache MINA Vulnerable to Deserialization of Untrusted Data (CVE-2024-52046 Incomplete Fix)
critical9.8Apr 27, 2026CVE-2026-41635
Apache MINA vulnerable to Deserialization of Untrusted Data
critical9.8Apr 27, 2026
