# CVE-2018-8018: Code execution via deserialization in org.apache.ignite:ignite-core

Source: https://junglewise.ai/threats/cve-2018-8018-code-execution-via-deserialization-in-org-apache-ignite-ignite  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2018-10-16  
License: CC BY 4.0 with a link back

CVE-2018-8018 · Severity: low · CVSS 3 · Published 2018-10-16

Code execution via deserialization in org.apache.ignite:ignite-core

Technologies: [org.apache.ignite:ignite-core (Maven)](https://junglewise.ai/threats/technologies/org-apache-ignite-ignite-core). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2018-8018 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2018-8018 being exploited in the wild.

**How severe is CVE-2018-8018?** Low severity, with a CVSS score of 3, published 16 October 2018.

**Which products and versions are affected?** org.apache.ignite:ignite-core (Maven) ECOSYSTEM:introduced=0,fixed=2.6.

**Is there a fix for CVE-2018-8018?** Yes. org.apache.ignite:ignite-core (Maven): upgrade to 2.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2018-8018?** Check whether you run org.apache.ignite:ignite-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.apache.ignite:ignite-core (Maven): upgrade to 2.6 or later

  ```sh
  # set org.apache.ignite:ignite-core to 2.6 in your pom.xml or build.gradle
  ```


## Affected products

- org.apache.ignite:ignite-core (Maven) ECOSYSTEM:introduced=0,fixed=2.6

## Identifiers

- CVE-2018-8018
- GHSA-qcjv-wfcg-mmpr

## Related threats

- [Apache Ignite path traversal in REST API](https://junglewise.ai/threats/cve-2025-48977-apache-ignite-path-traversal-in-rest-api)
- [Apache Ignite: Possible RCE when deserializing incoming messages by the server node](https://junglewise.ai/threats/cve-2024-52577-apache-ignite-possible-rce-when-deserializing-incoming-messages)
- [File system access via H2 in Apache Ignite](https://junglewise.ai/threats/cve-2020-1963-file-system-access-via-h2-in-apache-ignite)
- [Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization](https://junglewise.ai/threats/cve-2018-1295-apache-serialization-mechanism-does-not-have-a-list-of-classes)
- [Moderate severity vulnerability that affects org.apache.ignite:ignite-core](https://junglewise.ai/threats/cve-2016-6805-moderate-severity-vulnerability-that-affects-org-apache-ignite)