CVE-2018-1295 Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization

What is CVE-2018-1295?

CVE-2018-1295 is a critical unsafe deserialization vulnerability in Apache Ignite, published on 2 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer.

Weakness: CWE-502

Which versions are affected by CVE-2018-1295?

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

Products include Apache Ignite.

How do I fix CVE-2018-1295?

Upgrade org.apache.ignite:ignite-core to 2.4 or later.

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

Is CVE-2018-1295 being exploited?

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

Other vulnerabilities in Apache Ignite

• CVE-2018-1273 VMware Tanzu Spring Data Commons Property Binder Exploited Critical 9.8
• CVE-2018-8018 Code execution via deserialization in org.apache.ignite:ignite-core Critical 9.8
• CVE-2024-52577 Apache Ignite: Possible RCE when deserializing incoming messages by the server node Critical 9.5
• CVE-2020-1963 File system access via H2 in Apache Ignite Critical 9.1
• CVE-2025-48977 Apache Ignite: REST HTTP arbitrary file read vulnerability High 8.5

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-chp4-rv79-68j3.