CVE-2018-8018

In Apache Ignite before 2.4.8 and 2.5.x before 2.5.3, 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 GridClientJdkMarshaller deserialization endpoint.

Published: 2018-07-20 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-8018 is rated High Risk (74.1/100): CVSS Critical severity, with high exploitation likelihood (EPSS 6.79%, 93th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +2.34% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-8018

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 4.45% 6.79% +2.34%
2 2026-02-02 4.67% 4.45% -0.23%
3 2025-10-16 — 4.67% —

Full EPSS history (20 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-8018

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2018-8018

GitHub Security Advisory for CVE-2018-8018

GHSA-qcjv-wfcg-mmpr · Severity: critical · Ecosystem: maven — Code execution via deserialization in org.apache.ignite:ignite-core

OS Trackers for CVE-2018-8018

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2018-8018

Affected software / configurations for CVE-2018-8018

Vendor Product Version Raw CPE
apache ignite < 2.4.8 cpe:2.3:a:apache:ignite:*:*:*:*:*:*:*:*
apache ignite > 2.5.0, < 2.5.3 cpe:2.3:a:apache:ignite:*:*:*:*:*:*:*:*

References for CVE-2018-8018

cvelogic Threat Intelligence