VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

hono: vulnerability history, versions and safety

hono is a package in the npm ecosystem. Vulert records 56 vulnerabilities for it across 120 releases, from Dec 2023 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
56 vulnerabilities recorded H7 M44 L5
i
3 with no fix published

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

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

Most recent disclosure 20 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all hono vulnerabilities

Vulert verdict on hono 4.13.13 i

Updated on 23 Oct 2026

Careful: 4.13.13 has 3 known vulnerabilities, and 3 have 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 Active

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 4.13.13 — affected i
  • Vulnerabilities on record 56 over 2 years · 49 in the last year i
  • Latest disclosure 20 Oct 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 3 i
  • Depended on by 99,702 packages i
  • Stars 32,629 i
  • Last release this month i
  • Licence MIT 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 hono, 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
5.0.0-rc.1 10 Oct 2026 M2 L1 MIT No Details →
5.0.0-rc.0 08 Oct 2026 M2 L1 MIT No Details →
4.13.13 04 Oct 2026 M2 L1 MIT No Details →
4.13.12 30 Sep 2026 M2 L1 MIT No Details →
4.13.11 29 Sep 2026 M2 L1 MIT No Details →
4.13.10 28 Sep 2026 M3 L1 MIT No Details →
4.13.9 24 Sep 2026 M3 L1 MIT No Details →
4.13.8 15 Sep 2026 M3 L1 MIT No Details →
4.13.7 04 Sep 2026 M3 L1 MIT No Details →
4.13.6 04 Sep 2026 M4 L1 MIT No Details →
4.13.5 26 Aug 2026 M4 L1 MIT No Details →
4.13.4 24 Aug 2026 M7 L1 MIT No Details →
4.13.3 18 Aug 2026 M7 L1 MIT No Details →
4.13.2 13 Aug 2026 M7 L1 MIT No Details →
4.13.1 07 Aug 2026 M7 L1 MIT No Details →
4.13.0 03 Aug 2026 M7 L1 MIT No Details →
4.12.34 03 Aug 2026 M7 L1 MIT No Details →
4.12.33 31 Jul 2026 M10 L2 MIT No Details →
4.12.32 24 Jul 2026 M10 L2 MIT No Details →
4.12.31 18 Jul 2026 M10 L2 MIT No Details →
4.12.30 13 Jul 2026 M10 L2 MIT No Details →
4.12.29 10 Jul 2026 M10 L2 MIT No Details →
4.12.28 06 Jul 2026 M10 L2 MIT No Details →
4.12.27 23 Jun 2026 M10 L2 MIT No Details →
4.12.26 18 Jun 2026 M13 L2 MIT No Details →
4.12.25 09 Jun 2026 M13 L2 MIT No Details →
4.12.24 08 Jun 2026 H1 M17 L2 MIT No Details →
4.12.23 25 May 2026 H1 M17 L2 MIT No Details →
4.12.22 22 May 2026 H1 M17 L2 MIT No Details →
4.12.21 19 May 2026 H1 M17 L2 MIT No Details →
4.12.20 19 May 2026 H1 M21 L2 MIT No Details →
4.12.19 16 May 2026 H1 M21 L2 MIT No Details →
4.12.18 06 May 2026 H1 M21 L2 MIT No Details →
4.12.17 05 May 2026 H1 M23 L3 MIT No Details →
4.12.16 30 Apr 2026 H1 M23 L3 MIT No Details →
4.12.15 24 Apr 2026 H1 M25 L3 MIT No Details →
4.12.14 15 Apr 2026 H1 M25 L3 MIT No Details →
4.12.13 15 Apr 2026 H1 M26 L3 MIT No Details →
4.12.12 07 Apr 2026 H1 M26 L3 MIT No Details →
4.12.11 06 Apr 2026 H1 M32 L3 MIT No Details →
4.12.10 02 Apr 2026 H1 M32 L3 MIT No Details →
4.12.9 23 Mar 2026 H1 M32 L3 MIT No Details →
4.12.8 14 Mar 2026 H1 M32 L3 MIT No Details →
4.12.7 10 Mar 2026 H1 M32 L3 MIT No Details →
4.12.6 10 Mar 2026 H1 M33 L3 MIT No Details →
4.12.5 04 Mar 2026 H1 M33 L3 MIT No Details →
4.12.4 03 Mar 2026 H1 M33 L3 MIT No Details →
4.12.3 26 Feb 2026 H2 M34 L3 MIT No Details →
4.12.2 23 Feb 2026 H2 M34 L3 MIT No Details →
4.12.1 21 Feb 2026 H3 M34 L3 MIT No Details →
4.12.0 19 Feb 2026 H3 M34 L3 MIT No Details →
4.11.10 18 Feb 2026 H2 M33 L3 MIT No Details →
4.11.9 08 Feb 2026 H2 M33 L4 MIT No Details →
4.11.8 06 Feb 2026 H2 M33 L4 MIT No Details →
4.11.7 27 Jan 2026 H2 M32 L4 MIT No Details →
4.11.6 26 Jan 2026 H2 M36 L4 MIT No Details →
4.11.5 22 Jan 2026 H2 M36 L4 MIT No Details →
4.11.4 13 Jan 2026 H2 M36 L4 MIT No Details →
4.11.3 26 Dec 2025 H4 M36 L4 MIT No Details →
4.11.2 25 Dec 2025 H4 M36 L4 MIT No Details →
4.11.1 14 Dec 2025 H4 M36 L4 MIT No Details →
4.11.0 13 Dec 2025 H4 M36 L4 MIT No Details →
4.10.8 09 Dec 2025 H4 M36 L4 MIT No Details →
4.10.7 26 Nov 2025 H4 M36 L4 MIT No Details →
4.10.6 14 Nov 2025 H4 M36 L4 MIT No Details →
4.10.5 11 Nov 2025 H4 M36 L4 MIT No Details →
4.10.4 30 Oct 2025 H4 M36 L4 MIT No Details →
4.10.3 24 Oct 2025 H4 M36 L4 MIT No Details →
4.10.2 21 Oct 2025 H4 M37 L4 MIT No Details →
4.10.1 17 Oct 2025 H5 M37 L4 MIT No Details →
4.10.0 16 Oct 2025 H5 M37 L4 MIT No Details →
4.9.12 13 Oct 2025 H5 M37 L4 MIT No Details →
4.9.11 11 Oct 2025 H5 M37 L4 MIT No Details →
4.9.10 05 Oct 2025 H5 M37 L4 MIT No Details →
4.9.9 26 Sep 2025 H5 M37 L4 MIT No Details →
4.9.8 18 Sep 2025 H5 M37 L4 MIT No Details →
4.9.7 12 Sep 2025 H5 M37 L4 MIT No Details →
4.9.6 03 Sep 2025 H5 M38 L4 MIT No Details →
4.9.5 29 Aug 2025 H6 M38 L4 MIT No Details →
4.9.4 22 Aug 2025 H6 M38 L4 MIT No Details →
4.9.3 22 Aug 2025 H6 M38 L4 MIT No Details →
4.9.2 15 Aug 2025 H6 M38 L4 MIT No Details →
4.9.1 12 Aug 2025 H6 M38 L4 MIT No Details →
4.9.0 07 Aug 2025 H6 M38 L4 MIT No Details →
4.8.12 02 Aug 2025 H6 M38 L4 MIT No Details →
4.8.11 01 Aug 2025 H6 M38 L4 MIT No Details →
4.8.10 29 Jul 2025 H6 M38 L4 MIT No Details →
4.8.9 26 Jul 2025 H6 M38 L4 MIT No Details →
4.8.8 25 Jul 2025 H6 M38 L4 MIT No Details →
4.8.7 25 Jul 2025 H6 M38 L4 MIT No Details →
4.8.6 25 Jul 2025 H6 M38 L4 MIT No Details →
4.8.5 14 Jul 2025 H6 M38 L4 MIT No Details →
4.8.4 04 Jul 2025 H6 M38 L4 MIT No Details →
4.8.3 24 Jun 2025 H6 M38 L4 MIT No Details →
4.8.2 20 Jun 2025 H6 M38 L4 MIT No Details →
4.8.1 19 Jun 2025 H6 M38 L4 MIT No Details →
4.8.0 17 Jun 2025 H6 M38 L4 MIT No Details →
4.7.11 31 May 2025 H5 M38 L4 MIT No Details →
4.7.10 17 May 2025 H5 M38 L4 MIT No Details →
4.7.9 09 May 2025 H5 M38 L4 MIT No Details →
4.7.8 28 Apr 2025 H5 M38 L4 — No Details →
4.7.7 15 Apr 2025 H5 M38 L4 — No Details →
4.7.6 08 Apr 2025 H5 M38 L4 — No Details →
4.7.5 20 Mar 2025 H5 M38 L4 — No Details →
4.7.4 05 Mar 2025 H5 M38 L4 — No Details →
4.7.3 05 Mar 2025 H5 M38 L4 — No Details →
4.7.2 18 Feb 2025 H5 M38 L4 — No Details →
4.7.1 13 Feb 2025 H5 M38 L4 — No Details →
4.7.0 07 Feb 2025 H5 M38 L4 — No Details →
4.6.20 31 Jan 2025 H5 M38 L3 — No Details →
4.6.19 26 Jan 2025 H5 M38 L3 — No Details →
4.6.18 23 Jan 2025 H5 M38 L3 — No Details →
4.6.17 18 Jan 2025 H5 M38 L3 — No Details →
4.6.16 05 Jan 2025 H5 M38 L3 — No Details →
4.6.15 28 Dec 2024 H5 M38 L3 — No Details →
4.6.14 14 Dec 2024 H5 M38 L3 — No Details →
4.6.13 06 Dec 2024 H5 M38 L3 — No Details →
4.6.12 25 Nov 2024 H5 M38 L3 — No Details →
4.6.11 19 Nov 2024 H5 M38 L3 — No Details →
4.6.10 13 Nov 2024 H5 M38 L3 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 3
  • 2025 4
  • 2026 48

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

03 Vulnerabilities

Recorded vulnerabilities for hono

The 5 most severe of 56 vulnerabilities recorded for this package

Search all 56 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27700: Hono Package Vulnerable to Authentication Bypass via IP Spoofing 8.2 high 4.12.2 25 Feb 2026
CVE-2026-22817: Hono Package JWT Algorithm Confusion Vulnerability Leading to Token Forgery 8.2 high 4.11.4 13 Jan 2026
CVE-2026-22818: Hono Package Suffers from JWT Algorithm Confusion Vulnerability 8.2 high 4.11.4 13 Jan 2026
Hono Package Vulnerability: Improper Authorization via JWT Audience Validation 8.1 high 4.10.2 22 Oct 2025
CVE-2026-29045: Hono Package Arbitrary File Access Vulnerability 7.5 high 4.12.4 04 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: 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 hono

Is hono safe to use?

Vulert records 56 vulnerabilities for hono in npm: 0 critical, 7 high, 44 medium and 5 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is hono's Vulert package health score?

Vulert scores hono 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 hono affected?

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

Which version of hono should I use?

4.13.13 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 hono have?

56 vulnerabilities are recorded for hono in the npm ecosystem: 0 critical, 7 high, 44 medium and 5 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new hono vulnerabilities disclosed?

49 vulnerabilities were recorded for hono in the last 12 months, and the oldest entry in this database dates to 15 Dec 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 hono 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 hono for upcoming vulnerabilities?

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