SOC status:Duty analyst on shift

UK Cyber Defence
VulnerabilityModified

CVE-2018-1295

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.

CRITICAL 9.8EPSS 6.35%

Does this matter?

High impact if exploited, but EPSS currently rates exploitation as unlikely (6.35%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.

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.

CVSS 3.0
9.8 CRITICALCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
6.35% probability · 94th percentile
Public exploits
None in Exploit-DB
CISA KEV
Not listed
Weakness
CWE-502
Affected
apache/ignite
Source
security@apache.org
EPSS trend
0%5%10%27 October 2026: 6.35%27 October 202627 October 2026

EPSS 6.3% since 27 October 2026; no change recorded yet. The dashed line is the ten per cent mark our analysts treat as “patch before the next change window”. Points are recorded when the score first appears and whenever it moves by a percentage point or more.

References

Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.