VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

h2: vulnerability history, versions and safety

h2 is a package in the crates.io ecosystem. Vulert records 8 vulnerabilities for it across 83 releases, from Apr 2023 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded M3 U5
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 17 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all h2 vulnerabilities

Vulert verdict on h2 0.4.20 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 0.4.20 — unaffected i
  • Vulnerabilities on record 8 over 3 years · 1 in the last year i
  • Latest disclosure 17 Aug 2026 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Stars 1,556 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, 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 h2, 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
0.4.20 06 Oct 2026 none MIT — Details →
0.4.19 24 Aug 2026 none MIT — Details →
0.4.18 20 Aug 2026 none MIT — Details →
0.4.17 19 Aug 2026 none MIT — Details →
0.4.16 17 Aug 2026 none MIT — Details →
0.4.15 15 Jun 2026 U1 MIT Yes Details →
0.4.14 04 May 2026 U1 MIT Yes Details →
0.4.13 05 Jan 2026 U1 MIT Yes Details →
0.4.12 06 Aug 2025 U1 MIT Yes Details →
0.3.27 11 Jul 2025 U1 MIT Yes Details →
0.4.11 30 Jun 2025 U1 MIT Yes Details →
0.4.10 05 May 2025 U1 MIT Yes Details →
0.4.9 14 Apr 2025 U1 MIT Yes Details →
0.4.8 18 Feb 2025 U1 MIT Yes Details →
0.4.7 19 Nov 2024 U1 MIT Yes Details →
0.4.6 19 Aug 2024 U1 MIT Yes Details →
0.4.5 17 May 2024 U1 MIT Yes Details →
0.4.4 03 Apr 2024 U1 MIT Yes Details →
0.3.26 03 Apr 2024 U1 MIT Yes Details →
0.4.3 15 Mar 2024 U1 MIT Yes Details →
0.3.25 15 Mar 2024 M1 U2 MIT Yes Details →
0.4.2 17 Jan 2024 U1 MIT Yes Details →
0.3.24 17 Jan 2024 M1 U2 MIT Yes Details →
0.3.23 10 Jan 2024 M2 U3 MIT Yes Details →
0.4.1 08 Jan 2024 U1 MIT Yes Details →
0.4.0 15 Nov 2023 U1 MIT Yes Details →
0.3.22 15 Nov 2023 M2 U3 MIT Yes Details →
0.3.21 21 Aug 2023 M2 U3 MIT Yes Details →
0.3.20 26 Jun 2023 M2 U3 MIT Yes Details →
0.3.19 12 May 2023 M2 U3 MIT Yes Details →
0.3.18 17 Apr 2023 M2 U3 MIT Yes Details →
0.3.17 13 Apr 2023 M2 U3 MIT Yes Details →
0.3.16 27 Feb 2023 M3 U5 MIT Yes Details →
0.3.15 24 Oct 2022 M3 U5 MIT Yes Details →
0.3.14 16 Aug 2022 M3 U5 MIT Yes Details →
0.3.13 31 Mar 2022 M3 U5 MIT Yes Details →
0.3.12 09 Mar 2022 M3 U5 MIT Yes Details →
0.3.11 26 Jan 2022 M3 U5 MIT Yes Details →
0.3.10 07 Jan 2022 M3 U5 MIT Yes Details →
0.3.9 09 Dec 2021 M3 U5 MIT Yes Details →
0.3.8 08 Dec 2021 M3 U5 MIT Yes Details →
0.3.7 22 Oct 2021 M3 U5 MIT Yes Details →
0.3.6 30 Sep 2021 M3 U5 MIT Yes Details →
0.3.5 29 Sep 2021 M3 U5 MIT Yes Details →
0.3.4 20 Aug 2021 M3 U5 MIT Yes Details →
0.3.3 29 Apr 2021 M3 U5 MIT Yes Details →
0.3.2 25 Mar 2021 M3 U5 MIT Yes Details →
0.3.1 26 Feb 2021 M3 U5 MIT Yes Details →
0.3.0 23 Dec 2020 M3 U5 MIT Yes Details →
0.2.7 23 Oct 2020 M3 U5 MIT Yes Details →
0.2.6 13 Jul 2020 M3 U5 MIT Yes Details →
0.2.5 06 May 2020 M3 U5 MIT Yes Details →
0.2.4 30 Mar 2020 M3 U5 MIT Yes Details →
0.2.3 25 Mar 2020 M3 U5 MIT Yes Details →
0.2.2 03 Mar 2020 M3 U5 MIT Yes Details →
0.2.1 06 Dec 2019 M3 U5 MIT Yes Details →
0.2.0 03 Dec 2019 M3 U5 MIT Yes Details →
0.2.0-alpha.3 01 Oct 2019 M3 U5 MIT Yes Details →
0.2.0-alpha.2 20 Sep 2019 M3 U5 MIT Yes Details →
0.2.0-alpha.1 04 Sep 2019 M3 U5 MIT Yes Details →
0.1.26 26 Jul 2019 M3 U5 MIT Yes Details →
0.1.25 28 Jun 2019 M3 U5 MIT Yes Details →
0.1.24 17 Jun 2019 M3 U5 MIT Yes Details →
0.1.23 05 Jun 2019 M3 U5 MIT Yes Details →
0.1.22 03 Jun 2019 M3 U5 MIT Yes Details →
0.1.21 30 May 2019 M3 U5 MIT Yes Details →
0.1.20 16 May 2019 M3 U5 MIT Yes Details →
0.1.19 15 May 2019 M3 U5 MIT Yes Details →
0.1.18 09 Apr 2019 M3 U5 MIT Yes Details →
0.1.17 13 Mar 2019 M3 U5 MIT Yes Details →
0.1.16 24 Jan 2019 M3 U5 MIT Yes Details →
0.1.15 13 Jan 2019 M3 U5 MIT Yes Details →
0.1.14 05 Dec 2018 M3 U5 MIT Yes Details →
0.1.13 16 Oct 2018 M3 U5 MIT Yes Details →
0.1.12 08 Aug 2018 M3 U5 MIT Yes Details →
0.1.11 31 Jul 2018 M3 U5 MIT Yes Details →
0.1.10 18 Jun 2018 M3 U5 MIT Yes Details →
0.1.9 31 May 2018 M3 U5 MIT Yes Details →
0.1.8 23 May 2018 M3 U5 MIT Yes Details →
0.1.7 14 May 2018 M3 U5 MIT Yes Details →
0.1.6 25 Apr 2018 M3 U5 MIT Yes Details →
0.1.5 07 Apr 2018 M3 U5 MIT Yes Details →
0.1.4 05 Apr 2018 M3 U5 MIT Yes Details →
0.1.3 28 Mar 2018 M3 U5 MIT Yes Details →
0.1.2 14 Mar 2018 M3 U5 MIT Yes Details →
0.1.1 08 Mar 2018 M3 U5 MIT Yes Details →
0.1.0 12 Jan 2018 M3 U5 MIT Yes Details →
0.0.0 09 Mar 2017 M3 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3
  • 2024 4
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for h2

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
h2 servers vulnerable to CONTINUATION Flood 5.3 medium 0.3.26 05 Apr 2024
CVE-2023-26964: h2 vulnerable to denial of service N/A unrated 0.3.17 14 Apr 2023
CVE-2023-26964: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS) N/A unrated 0.3.17 14 Apr 2023
CVE-2023-26964: h2 vulnerable to denial of service N/A medium 0.3.17 11 Apr 2023
Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS) N/A unrated 0.3.24 17 Jan 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 h2

Is h2 safe to use?

Vulert records 8 vulnerabilities for h2 in crates.io: 0 critical, 0 high, 3 medium and 0 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is h2's Vulert package health score?

Vulert scores h2 73/100, which reads as in good shape. 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 h2 affected?

No. 0.4.20, 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 h2 should I use?

0.4.20 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 h2 have?

8 vulnerabilities are recorded for h2 in the crates.io ecosystem: 0 critical, 0 high, 3 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new h2 vulnerabilities disclosed?

1 vulnerability was recorded for h2 in the last 12 months, and the oldest entry in this database dates to 11 Apr 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 h2 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 h2 for upcoming vulnerabilities?

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