Vulnerability Database · npm · h3 · Version

h3 2.0.1-rc.17

2.0.1-rc.17 is affected by 3 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 1 Medium 2 Low 0 Unrated 0

Released 19 Mar 2026 Licence MIT Also known from other sources 2 Newer releases 160 Database updated 23/Oct/2026

Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version

h3 2.0.1-rc.17 vulnerabilities

3 vulnerabilities cover h3 2.0.1-rc.17. Open the full list in the database.

Looking for another version, or everything Vulert holds for h3?

All versions → Full vulnerability list →

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 2.0.1-rc.17

Is h3 2.0.1-rc.17 vulnerable?

Yes. 3 vulnerabilities in the Vulert database cover h3 2.0.1-rc.17: 0 critical, 1 high, 2 medium and 0 low. Each entry above names the fixed version to move to.

Is 2.0.1-rc.17 the latest release of h3?

No. 2.0.1-rc.17 was published 19 Mar 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.