VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

ai.h2o:h2o-core: vulnerability history, versions and safety

ai.h2o:h2o-core is a package in the Maven ecosystem. Vulert records 6 vulnerabilities for it across 120 releases, from Nov 2023 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C4 H1 M1
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 23 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ai.h2o:h2o-core vulnerabilities

Vulert verdict on ai.h2o:h2o-core 3.46.0.12 i

Updated on 23 Oct 2026

Careful: 3.46.0.12 has 5 known vulnerabilities, and 5 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 3.46.0.12 — affected i
  • Vulnerabilities on record 6 over 2 years · 2 in the last year i
  • Latest disclosure 23 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i
  • Depended on by 22 packages i
  • Stars 7,511 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 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 ai.h2o:h2o-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
3.46.0.12 11 Aug 2026 C4 H1 Apache-2.0 No Details →
3.46.0.11 22 May 2026 C4 H1 Apache-2.0 No Details →
3.46.0.10 12 Mar 2026 C4 H1 Apache-2.0 No Details →
3.46.0.9 24 Nov 2025 M1 Apache-2.0 Yes Details →
3.46.0.8 08 Oct 2025 M1 Apache-2.0 Yes Details →
3.46.0.7 27 Mar 2025 C2 M1 Apache-2.0 No Details →
3.46.0.6 02 Nov 2024 C2 M1 Apache-2.0 No Details →
3.46.0.5 29 Aug 2024 C2 M1 Apache-2.0 No Details →
3.46.0.4 09 Jul 2024 C2 H1 M1 Apache-2.0 No Details →
3.46.0.3 11 Jun 2024 C2 H1 M1 Apache-2.0 No Details →
3.46.0.2 13 May 2024 C2 H1 M1 Apache-2.0 No Details →
3.46.0.1 13 Mar 2024 C3 H1 M1 Apache-2.0 No Details →
3.44.0.3 20 Dec 2023 C3 H1 M1 Apache-2.0 No Details →
3.44.0.2 08 Nov 2023 C3 H1 M1 Apache-2.0 No Details →
3.44.0.1 16 Oct 2023 C3 H1 M1 Apache-2.0 No Details →
3.42.0.4 03 Oct 2023 C3 H1 M1 Apache-2.0 No Details →
3.42.0.3 22 Aug 2023 C3 H1 M1 Apache-2.0 No Details →
3.42.0.2 25 Jul 2023 C3 H1 M1 Apache-2.0 No Details →
3.42.0.1 20 Jun 2023 C3 H1 M1 Apache-2.0 No Details →
3.40.0.4 28 Apr 2023 C4 H1 M1 Apache-2.0 No Details →
3.40.0.3 04 Apr 2023 C4 H1 M1 Apache-2.0 No Details →
3.40.0.2 09 Mar 2023 C4 H1 M1 Apache-2.0 No Details →
3.40.0.1 08 Feb 2023 C4 H1 M1 Apache-2.0 No Details →
3.38.0.4 05 Jan 2023 C4 H1 M1 Apache-2.0 No Details →
3.38.0.3 23 Nov 2022 C4 H1 M1 Apache-2.0 No Details →
3.38.0.2 27 Oct 2022 C4 H1 M1 Apache-2.0 No Details →
3.38.0.1 19 Sep 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.1.5 15 Sep 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.1.4 03 Aug 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.1.3 08 Jul 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.1.2 26 May 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.1.1 13 Apr 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.0.4 30 Mar 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.0.3 16 Feb 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.0.2 25 Jan 2022 C4 H1 M1 Apache-2.0 No Details →
3.34.0.8 13 Jan 2022 C4 H1 M1 Apache-2.0 No Details →
3.36.0.1 29 Dec 2021 C4 H1 M1 Apache-2.0 No Details →
3.34.0.7 21 Dec 2021 C4 H1 M1 Apache-2.0 No Details →
3.34.0.6 15 Dec 2021 C4 H1 M1 Apache-2.0 No Details →
3.34.0.5 13 Dec 2021 C4 H1 M1 Apache-2.0 No Details →
3.34.0.4 17 Nov 2021 C4 H1 M1 Apache-2.0 No Details →
3.34.0.3 07 Oct 2021 C4 H1 M1 Apache-2.0 No Details →
3.35.0.2 06 Oct 2021 C4 H1 M1 Apache-2.0 No Details →
3.34.0.1 14 Sep 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.1.7 02 Sep 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.1.6 19 Aug 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.1.5 04 Aug 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.1.4 08 Jul 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.1.3 19 May 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.1.2 29 Apr 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.1.1 25 Mar 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.0.5 16 Mar 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.0.4 01 Feb 2021 C4 H1 M1 Apache-2.0 No Details →
3.32.0.3 24 Dec 2020 C4 H1 M1 Apache-2.0 No Details →
3.32.0.2 17 Nov 2020 C4 H1 M1 Apache-2.0 No Details →
3.32.0.1 08 Oct 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.1.3 28 Sep 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.1.2 03 Sep 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.1.1 10 Aug 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.0.7 21 Jul 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.0.6 30 Jun 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.0.5 18 Jun 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.0.4 01 Jun 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.0.3 13 May 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.0.2 29 Apr 2020 C4 H1 M1 Apache-2.0 No Details →
3.30.0.1 03 Apr 2020 C4 H1 M1 Apache-2.0 No Details →
3.28.1.3 02 Apr 2020 C4 H1 M1 Apache-2.0 No Details →
3.28.1.2 17 Mar 2020 C4 H1 M1 Apache-2.0 No Details →
3.28.1.1 05 Mar 2020 C4 H1 M1 Apache-2.0 No Details →
3.28.0.4 23 Feb 2020 C4 H1 M1 Apache-2.0 No Details →
3.28.0.3 05 Feb 2020 C4 H1 M1 Apache-2.0 No Details →
3.28.0.2 20 Jan 2020 C4 H1 M1 Apache-2.0 No Details →
3.28.0.1 16 Dec 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.11 05 Dec 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.10 07 Nov 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.9 29 Oct 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.8 18 Oct 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.6 02 Oct 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.5 16 Sep 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.4 13 Sep 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.3 24 Aug 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.2 26 Jul 2019 C4 H1 M1 Apache-2.0 No Details →
3.26.0.1 15 Jul 2019 C4 H1 M1 Apache-2.0 No Details →
3.24.0.5 19 Jun 2019 C4 H1 M1 Apache-2.0 No Details →
3.24.0.4 29 May 2019 C4 H1 M1 Apache-2.0 No Details →
3.24.0.3 07 May 2019 C4 H1 M1 Apache-2.0 No Details →
3.24.0.2 17 Apr 2019 C4 H1 M1 Apache-2.0 No Details →
3.24.0.1 01 Apr 2019 C4 H1 M1 Apache-2.0 No Details →
3.22.1.6 13 Mar 2019 C4 H1 M1 Apache-2.0 No Details →
3.22.1.5 05 Mar 2019 C4 H1 M1 Apache-2.0 No Details →
3.22.1.4 15 Feb 2019 C4 H1 M1 Apache-2.0 No Details →
3.22.1.3 25 Jan 2019 C4 H1 M1 Apache-2.0 No Details →
3.22.1.2 19 Jan 2019 C4 H1 M1 Apache-2.0 No Details →
3.22.0.5 16 Jan 2019 C4 H1 M1 Apache-2.0 No Details →
3.22.0.4 04 Jan 2019 C4 H1 M1 Apache-2.0 No Details →
3.22.1.1 28 Dec 2018 C4 H1 M1 Apache-2.0 No Details →
3.22.0.3 22 Dec 2018 C4 H1 M1 Apache-2.0 No Details →
3.22.0.2 22 Nov 2018 C4 H1 M1 Apache-2.0 No Details →
3.22.0.1 26 Oct 2018 C4 H1 M1 Apache-2.0 No Details →
3.20.0.10 16 Oct 2018 C4 H1 M1 Apache-2.0 No Details →
3.20.0.9 01 Oct 2018 C4 H1 M1 — No Details →
3.20.0.8 21 Sep 2018 C4 H1 M1 — No Details →
3.20.0.7 01 Sep 2018 C4 H1 M1 — No Details →
3.20.0.6 25 Aug 2018 C4 H1 M1 — No Details →
3.20.0.5 09 Aug 2018 C4 H1 M1 — No Details →
3.20.0.4 31 Jul 2018 C4 H1 M1 — No Details →
3.20.0.3 11 Jul 2018 C4 H1 M1 — No Details →
3.20.0.2 15 Jun 2018 C4 H1 M1 — No Details →
3.20.0.1 07 Jun 2018 C4 H1 M1 — No Details →
3.18.0.11 24 May 2018 C4 H1 M1 — No Details →
3.18.0.10 22 May 2018 C4 H1 M1 — No Details →
3.16.0.12 21 May 2018 C4 H1 M1 — No Details →
3.16.0.11 16 May 2018 C4 H1 M1 — No Details →
3.16.0.10 16 May 2018 C4 H1 M1 — No Details →
3.18.0.9 11 May 2018 C4 H1 M1 — No Details →
3.18.0.8 19 Apr 2018 C4 H1 M1 — No Details →
3.18.0.7 14 Apr 2018 C4 H1 M1 — No Details →
3.18.0.6 14 Apr 2018 C4 H1 M1 — No Details →
3.16.0.9 05 Apr 2018 C4 H1 M1 — No Details →
3.18.0.5 29 Mar 2018 C4 H1 M1 — No Details →

The newest 120 of 258 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 2
  • 2025 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for ai.h2o:h2o-core

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-6544: H2O Deserialization Vulnerability Allows Arbitrary Code Execution 9.8 critical No fix published 22 Sep 2025
CVE-2023-6038: H2O local file inclusion vulnerability 9.3 critical No fix published 16 Nov 2023
CVE-2024-45758: H2O.ai H2O Vulnerable to Deserialization Attacks via JDBC Connection URL 9.1 critical No fix published 06 Sep 2024
CVE-2024-5986: H2O Package Arbitrary File Write Vulnerability 9.1 critical No fix published 02 Feb 2026
CVE-2024-6960: H2O vulnerable to Deserialization of Untrusted Data 7.5 high No fix published 21 Jul 2024

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 ai.h2o:h2o-core

Is ai.h2o:h2o-core safe to use?

Vulert records 6 vulnerabilities for ai.h2o:h2o-core in Maven: 4 critical, 1 high, 1 medium and 0 low. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is ai.h2o:h2o-core's Vulert package health score?

Vulert scores ai.h2o:h2o-core 50/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of ai.h2o:h2o-core affected?

Yes. 3.46.0.12, the version you would install today, has 5 known vulnerabilities, and 5 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of ai.h2o:h2o-core should I use?

3.46.0.12 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 ai.h2o:h2o-core have?

6 vulnerabilities are recorded for ai.h2o:h2o-core in the Maven ecosystem: 4 critical, 1 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 ai.h2o:h2o-core vulnerabilities disclosed?

2 vulnerabilities were recorded for ai.h2o:h2o-core in the last 12 months, and the oldest entry in this database dates to 16 Nov 2023. 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 ai.h2o:h2o-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 ai.h2o:h2o-core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ai.h2o:h2o-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.