VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.ignite:ignite-core: vulnerability history, versions and safety

org.apache.ignite:ignite-core is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 36 releases, from Oct 2018 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded C4 H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 28 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.ignite:ignite-core vulnerabilities

Vulert verdict on org.apache.ignite:ignite-core 3.1.0 i

Updated on 23 Oct 2026

Good news: 3.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 62/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Stay on 3.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 7 over 7 years · 1 in the last year i
  • Latest disclosure 28 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 83 packages i
  • Stars 46 i
  • OpenSSF scorecard 3/10 i
  • Last release 12 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.ignite:ignite-core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.18.0 23 Apr 2026 none Apache-2.0 — Details →
3.1.0 21 Oct 2025 none — — Details →
2.17.0 09 Feb 2025 H1 Apache-2.0 Yes Details →
3.0.0 30 Jan 2025 none — — Details →
2.16.0 17 Dec 2023 C1 H1 Apache-2.0 Yes Details →
2.15.0 26 Apr 2023 C1 H1 Apache-2.0 Yes Details →
3.0.0-beta1 14 Nov 2022 none — — Details →
2.14.0 30 Sep 2022 C1 H1 Apache-2.0 Yes Details →
3.0.0-alpha5 09 Jun 2022 none Apache-2.0 — Details →
2.13.0 20 Apr 2022 C1 H1 Apache-2.0 Yes Details →
3.0.0-alpha4 25 Jan 2022 none Apache-2.0 — Details →
2.12.0 10 Jan 2022 C1 H1 Apache-2.0 Yes Details →
2.11.1 20 Dec 2021 C1 H1 Apache-2.0 Yes Details →
3.0.0-alpha3 12 Oct 2021 none Apache-2.0 — Details →
2.11.0 11 Sep 2021 C1 H1 Apache-2.0 Yes Details →
3.0.0-alpha2 25 Jun 2021 none Apache-2.0 — Details →
2.10.0 11 Mar 2021 C1 H1 Apache-2.0 Yes Details →
2.9.1 14 Dec 2020 C1 H1 Apache-2.0 Yes Details →
2.9.0 15 Oct 2020 C1 H1 Apache-2.0 Yes Details →
2.8.1 22 May 2020 C1 H1 Apache-2.0 Yes Details →
2.8.0 27 Feb 2020 C2 H1 Apache-2.0 Yes Details →
2.7.6 12 Sep 2019 C2 H1 Apache-2.0 Yes Details →
2.7.5 04 Jun 2019 C2 H1 Apache-2.0 Yes Details →
2.7.0 02 Dec 2018 C2 H1 Apache-2.0 Yes Details →
2.6.0 10 Jul 2018 C2 H1 Apache-2.0 Yes Details →
2.5.0 23 May 2018 C2 H1 Apache-2.0 Yes Details →
2.4.0 05 Mar 2018 C2 H1 Apache-2.0 Yes Details →
2.3.0 28 Oct 2017 C3 H1 Apache-2.0 Yes Details →
2.2.0 15 Sep 2017 C3 H1 Apache-2.0 Yes Details →
2.1.0 20 Jul 2017 C3 H1 Apache-2.0 Yes Details →
2.0.0 30 Apr 2017 C3 H2 Apache-2.0 Yes Details →
1.9.0 02 Mar 2017 C3 H1 Apache-2.0 Yes Details →
1.8.0 05 Dec 2016 C3 H1 M1 Apache-2.0 Yes Details →
1.7.0 01 Aug 2016 C3 H1 M1 Apache-2.0 Yes Details →
1.6.0 18 May 2016 C3 H1 M1 Apache-2.0 Yes Details →
1.5.0.final 29 Dec 2015 C3 H1 M1 Apache-2.0 Yes Details →
1.5.0-b1 01 Dec 2015 C3 H1 M1 Apache-2.0 Yes Details →
1.4.0 24 Sep 2015 C3 H1 M1 Apache-2.0 Yes Details →
1.3.0-incubating 10 Jul 2015 C3 H1 M1 Apache-2.0 Yes Details →
1.2.0-incubating 16 Jun 2015 C3 H1 M1 Apache-2.0 Yes Details →
1.1.0-incubating 20 May 2015 C3 H1 M1 Apache-2.0 Yes Details →
1.0.0 31 Mar 2015 C3 H1 M1 Apache-2.0 Yes Details →
1.0.0-RC3 24 Mar 2015 C3 H1 M1 Apache-2.0 Yes Details →
1.0.0-RC1 17 Feb 2015 C3 H1 M1 Apache-2.0 Yes Details →

All 44 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 4
  • 2020 1
  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.ignite:ignite-core

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1295: Apache Ignite 2.3 or earlier - Arbitrary Code Execution 9.8 critical 2.4 16 Oct 2018
CVE-2018-8018: Apache Ignite Ignite-core - Arbitrary Code Execution 9.8 critical 2.6 16 Oct 2018
CVE-2020-1963: File system access via H2 in Apache Ignite 9.1 critical 2.8.1 05 Jun 2020
CVE-2024-52577: Apache Ignite Core RCE Vulnerability Due to Ignored Class Serialization Filters 9.0 critical 2.17.0 14 Feb 2025
CVE-2017-7686: Apache Ignite External PHP Server Communication Vulnerability 7.5 high 2.1 16 Oct 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.ignite:ignite-core

Is org.apache.ignite:ignite-core safe to use?

Vulert records 7 vulnerabilities for org.apache.ignite:ignite-core in Maven: 4 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.ignite:ignite-core's Vulert package health score?

Vulert scores org.apache.ignite:ignite-core 62/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.apache.ignite:ignite-core affected?

No. 3.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.apache.ignite:ignite-core should I use?

3.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.ignite:ignite-core have?

7 vulnerabilities are recorded for org.apache.ignite:ignite-core in the Maven ecosystem: 4 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.ignite:ignite-core vulnerabilities disclosed?

1 vulnerability was recorded for org.apache.ignite:ignite-core in the last 12 months, and the oldest entry in this database dates to 16 Oct 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.ignite:ignite-core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.ignite:ignite-core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.ignite:ignite-core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.