VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

h3: vulnerability history, versions and safety

h3 is a package in the npm ecosystem. Vulert records 11 vulnerabilities for it across 117 releases, from Jan 2026 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded H4 M6 L1
i
1 with no fix published

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

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

Most recent disclosure 06 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all h3 vulnerabilities

Vulert verdict on h3 2.0.8 i

Updated on 22 Oct 2026

Careful: 2.0.8 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • 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 2.0.8 — affected i
  • Vulnerabilities on record 11 over 1 year · 11 in the last year i
  • Latest disclosure 06 Sep 2026 i
  • Highest CVSS 8.9 i
  • With no published fix 1 i
  • Stars 5,465 i
  • Last release this month i
  • Licence MIT i
  • Similar names he i

Version list, release dates, licence and dependants published by the npm registry, 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 h3, 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.0.8 22 Oct 2026 H1 MIT No Details →
2.0.7 20 Oct 2026 H1 MIT No Details →
2.0.6 20 Oct 2026 H1 MIT No Details →
2.0.5 18 Oct 2026 H1 MIT No Details →
2.0.4 18 Oct 2026 H1 MIT No Details →
2.0.3 17 Oct 2026 H1 MIT No Details →
2.0.2 07 Oct 2026 H1 MIT No Details →
2.0.1 03 Oct 2026 H1 MIT No Details →
2.0.1-rc.33 03 Oct 2026 H1 MIT No Details →
2.0.1-rc.32 14 Sep 2026 H1 MIT No Details →
2.0.1-rc.31 03 Sep 2026 H1 MIT No Details →
2.0.1-rc.30 02 Sep 2026 H1 MIT No Details →
2.0.1-rc.29 20 Aug 2026 H1 MIT No Details →
2.0.1-rc.28 20 Aug 2026 H1 MIT No Details →
2.0.1-rc.27 19 Aug 2026 H1 MIT No Details →
2.0.1-rc.26 24 Jul 2026 H1 MIT No Details →
2.0.1-rc.25 11 Jul 2026 H1 MIT No Details →
2.0.1-rc.24 10 Jul 2026 H1 MIT No Details →
2.0.1-rc.23 06 Jul 2026 H1 MIT No Details →
2.0.1-rc.22 05 May 2026 H1 MIT No Details →
2.0.1-rc.21 29 Apr 2026 H1 MIT No Details →
1.15.11 01 Apr 2026 none MIT — Details →
2.0.1-rc.20 27 Mar 2026 H1 MIT No Details →
2.0.1-rc.19 23 Mar 2026 H1 MIT No Details →
1.15.10 22 Mar 2026 none MIT — Details →
2.0.1-rc.18 21 Mar 2026 H1 MIT No Details →
2.0.1-rc.17 19 Mar 2026 M1 MIT Yes Details →
1.15.9 19 Mar 2026 none MIT — Details →
1.15.8 17 Mar 2026 M1 MIT Yes Details →
1.15.7 17 Mar 2026 M1 MIT Yes Details →
2.0.1-rc.16 09 Mar 2026 H1 M2 L1 MIT No Details →
2.0.1-rc.15 08 Mar 2026 H1 M2 L1 MIT No Details →
1.15.6 08 Mar 2026 M1 MIT Yes Details →
2.0.1-rc.14 05 Feb 2026 H3 M3 L1 MIT No Details →
2.0.1-rc.13 05 Feb 2026 H3 M3 L1 MIT No Details →
2.0.1-rc.12 05 Feb 2026 H3 M3 L1 MIT No Details →
2.0.1-rc.11 20 Jan 2026 H3 M3 L1 MIT No Details →
2.0.1-rc.10 20 Jan 2026 H3 M3 L1 MIT No Details →
2.0.1-rc.9 19 Jan 2026 H3 M3 L1 MIT No Details →
1.15.5 15 Jan 2026 M1 MIT Yes Details →
2.0.1-rc.8 15 Jan 2026 H3 M4 L1 MIT No Details →
2.0.1-rc.7 30 Dec 2025 H3 M4 L1 MIT No Details →
2.0.1-rc.6 08 Dec 2025 H3 M4 L1 MIT No Details →
2.0.1-rc.5 27 Oct 2025 H3 M4 L1 MIT No Details →
2.0.1-rc.4 25 Oct 2025 H3 M4 L1 MIT No Details →
2.0.1-rc.3 23 Oct 2025 H3 M4 L1 MIT No Details →
2.0.1-rc.2 08 Oct 2025 H3 M4 L1 MIT No Details →
2.0.1-rc.1 08 Oct 2025 H3 M4 L1 MIT No Details →
2.0.0-rc.1 07 Oct 2025 H1 M3 MIT No Details →
2.0.0-beta.5 01 Oct 2025 H1 M3 MIT No Details →
2.0.0-beta.4 27 Aug 2025 H1 M3 MIT No Details →
2.0.0-beta.3 30 Jul 2025 M2 MIT Yes Details →
2.0.0-beta.2 30 Jul 2025 M2 MIT Yes Details →
1.15.4 30 Jul 2025 H1 M1 MIT Yes Details →
2.0.0-beta.1 02 Jul 2025 M2 MIT Yes Details →
2.0.0-beta.0 10 Jun 2025 M2 MIT Yes Details →
1.15.3 28 Apr 2025 H1 M1 MIT Yes Details →
1.15.2 27 Apr 2025 H1 M1 MIT Yes Details →
1.15.1 22 Feb 2025 H1 M1 MIT Yes Details →
1.15.0 06 Feb 2025 H1 M1 MIT Yes Details →
1.14.0 22 Jan 2025 H1 M1 MIT Yes Details →
1.13.1 10 Jan 2025 H1 M1 MIT Yes Details →
1.13.0 03 Oct 2024 H1 M1 MIT Yes Details →
1.12.0 20 Jun 2024 H1 M1 MIT Yes Details →
1.11.1 25 Feb 2024 H1 M1 MIT Yes Details →
1.11.0 25 Feb 2024 H1 M1 MIT Yes Details →
1.10.2 19 Feb 2024 H1 M1 MIT Yes Details →
1.10.1 25 Jan 2024 H1 M1 MIT Yes Details →
1.10.0 04 Jan 2024 H1 M1 MIT Yes Details →
1.9.0 20 Nov 2023 H1 M1 MIT Yes Details →
1.8.2 26 Sep 2023 H1 M1 MIT Yes Details →
1.8.1 26 Aug 2023 H1 M1 MIT Yes Details →
1.8.0 15 Aug 2023 H1 M1 MIT Yes Details →
1.8.0-rc.3 07 Aug 2023 H1 M1 MIT Yes Details →
1.8.0-rc.2 02 Aug 2023 H1 M1 MIT Yes Details →
1.8.0-rc.1 31 Jul 2023 H1 M1 MIT Yes Details →
1.8.0-rc.0 31 Jul 2023 H1 M1 MIT Yes Details →
1.7.1 28 Jun 2023 H1 M1 MIT Yes Details →
1.7.0 20 Jun 2023 H1 M1 MIT Yes Details →
1.6.6 15 May 2023 H1 M1 MIT Yes Details →
1.6.5 05 May 2023 H1 M1 MIT Yes Details →
1.6.4 28 Mar 2023 H1 M1 MIT Yes Details →
1.6.3 28 Mar 2023 H1 M1 MIT Yes Details →
1.6.2 15 Mar 2023 H1 M1 MIT Yes Details →
1.6.1 15 Mar 2023 H1 M1 MIT Yes Details →
1.6.0 10 Mar 2023 H1 M1 MIT Yes Details →
1.5.0 16 Feb 2023 H1 M1 MIT Yes Details →
1.4.0 08 Feb 2023 H1 M1 MIT Yes Details →
1.3.0 08 Feb 2023 H1 M1 MIT Yes Details →
1.2.1 07 Feb 2023 H1 M1 MIT Yes Details →
1.2.0 06 Feb 2023 H1 M1 MIT Yes Details →
1.1.0 25 Jan 2023 H1 M1 MIT Yes Details →
1.0.2 13 Dec 2022 H1 M1 MIT Yes Details →
1.0.1 15 Nov 2022 H1 M1 MIT Yes Details →
0.8.6 27 Oct 2022 H1 M1 MIT Yes Details →
0.8.5 19 Oct 2022 H1 M1 MIT Yes Details →
0.8.4 18 Oct 2022 H1 M1 MIT Yes Details →
0.8.3 18 Oct 2022 H1 M1 MIT Yes Details →
0.8.2 17 Oct 2022 H1 M1 MIT Yes Details →
0.8.1 15 Oct 2022 H1 M1 MIT Yes Details →
0.8.0 15 Oct 2022 H1 M1 — Yes Details →
0.7.21 03 Sep 2022 H1 M1 — Yes Details →
0.7.20 03 Sep 2022 H1 M1 — Yes Details →
0.7.19 01 Sep 2022 H1 M1 — Yes Details →
0.7.18 01 Sep 2022 H1 M1 — Yes Details →
0.7.17 30 Aug 2022 H1 M1 — Yes Details →
0.7.16 23 Aug 2022 H1 M1 — Yes Details →
0.7.15 10 Aug 2022 H1 M1 — Yes Details →
0.7.14 08 Aug 2022 H1 M1 — Yes Details →
0.7.13 01 Aug 2022 H1 M1 — Yes Details →
0.7.12 21 Jul 2022 H1 M1 — Yes Details →
0.7.11 21 Jul 2022 H1 M1 — Yes Details →
0.7.10 17 Jun 2022 H1 M1 — Yes Details →
0.7.9 10 Jun 2022 H1 M1 — Yes Details →
0.7.8 04 May 2022 H1 M1 — Yes Details →
0.7.7 04 May 2022 H1 M1 — Yes Details →
0.7.6 29 Apr 2022 H1 M1 — Yes Details →
0.7.5 27 Apr 2022 H1 M1 — Yes Details →
0.7.4 14 Apr 2022 H1 M1 — Yes Details →
0.7.3 12 Apr 2022 H1 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 11

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

03 Vulnerabilities

Recorded vulnerabilities for h3

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-23527: h3 Package Request Smuggling Vulnerability 8.9 high 1.15.5 15 Jan 2026
CVE-2026-33128: h3 Package Suffers from Server-Sent Events Injection via Unsanitized Newlines 7.5 high 2.0.1-rc.15 18 Mar 2026
Denial of Service Vulnerability in h3 Package: Unbounded Chunked Cookie Count 7.5 high No fix published 06 Sep 2026
CVE-2026-33131: H3 Middleware Bypass Vulnerability Leading to Potential Data Exposure 7.4 high 2.0.1-rc.15 18 Mar 2026
CVE-2026-33129: h3 Package Timing Side-Channel Vulnerability in Basic Auth Utilities 5.9 medium 2.0.1-rc.9 18 Mar 2026

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 h3

Is h3 safe to use?

Vulert records 11 vulnerabilities for h3 in npm: 0 critical, 4 high, 6 medium and 1 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is h3's Vulert package health score?

Vulert scores h3 60/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 h3 affected?

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

How many vulnerabilities does h3 have?

11 vulnerabilities are recorded for h3 in the npm ecosystem: 0 critical, 4 high, 6 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new h3 vulnerabilities disclosed?

11 vulnerabilities were recorded for h3 in the last 12 months, and the oldest entry in this database dates to 15 Jan 2026. 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 h3 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 h3 for upcoming vulnerabilities?

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