VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

hapi: vulnerability history, versions and safety

hapi is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 120 releases, from Oct 2017 to Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H4 M3
i
1 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all hapi vulnerabilities

Vulert verdict on hapi 18.1.0 i

Updated on 22 Oct 2026

Careful: 18.1.0 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 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Key ecosystem project
  • Community Moderate

The registry marks the latest release as deprecated, 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 18.1.0 — affected i
  • Vulnerabilities on record 7 over 2 years · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 495 packages i
  • Stars 14,792 i
  • OpenSSF scorecard 3/10 i
  • Last release 92 months ago i
  • Licence non-standard i
  • Similar names @opentelemetry/api i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 hapi, 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
16.8.4 06 Jan 2024 H1 non-standard No Details →
17.8.5 19 Mar 2019 H1 BSD-3-Clause No Details →
18.1.0 04 Feb 2019 H1 BSD-3-Clause No Details →
17.8.4 04 Feb 2019 H1 BSD-3-Clause No Details →
18.0.1 31 Jan 2019 H1 BSD-3-Clause No Details →
17.8.3 31 Jan 2019 H1 BSD-3-Clause No Details →
17.8.2 31 Jan 2019 H1 BSD-3-Clause No Details →
18.0.0 18 Jan 2019 H1 BSD-3-Clause No Details →
17.8.1 23 Nov 2018 H1 BSD-3-Clause No Details →
17.8.0 23 Nov 2018 H1 BSD-3-Clause No Details →
16.7.0 06 Nov 2018 H1 BSD-3-Clause No Details →
17.7.0 06 Nov 2018 H1 BSD-3-Clause No Details →
16.6.5 05 Nov 2018 H1 BSD-3-Clause No Details →
17.6.4 03 Nov 2018 H1 BSD-3-Clause No Details →
16.6.4 02 Nov 2018 H1 BSD-3-Clause No Details →
17.6.3 02 Nov 2018 H1 BSD-3-Clause No Details →
17.6.2 01 Nov 2018 H1 BSD-3-Clause No Details →
17.6.1 01 Nov 2018 H1 BSD-3-Clause No Details →
17.6.0 25 Sep 2018 H1 BSD-3-Clause No Details →
17.5.5 23 Sep 2018 H1 BSD-3-Clause No Details →
17.5.4 28 Aug 2018 H1 BSD-3-Clause No Details →
17.5.3 02 Aug 2018 H1 BSD-3-Clause No Details →
17.5.2 24 Jun 2018 H1 BSD-3-Clause No Details →
17.5.1 30 May 2018 H1 BSD-3-Clause No Details →
17.5.0 21 May 2018 H1 BSD-3-Clause No Details →
17.4.0 29 Apr 2018 H1 BSD-3-Clause No Details →
17.3.1 02 Apr 2018 H1 BSD-3-Clause No Details →
17.3.0 31 Mar 2018 H1 BSD-3-Clause No Details →
17.2.3 16 Mar 2018 H1 BSD-3-Clause No Details →
17.2.2 07 Mar 2018 H1 BSD-3-Clause No Details →
16.6.3 01 Mar 2018 H1 BSD-3-Clause No Details →
17.2.1 01 Mar 2018 H1 BSD-3-Clause No Details →
17.2.0 20 Dec 2017 H1 BSD-3-Clause No Details →
17.1.1 23 Nov 2017 H1 BSD-3-Clause No Details →
17.1.0 23 Nov 2017 H1 BSD-3-Clause No Details →
17.0.2 21 Nov 2017 H1 BSD-3-Clause No Details →
17.0.1 05 Nov 2017 H1 BSD-3-Clause No Details →
17.0.0 03 Nov 2017 H1 BSD-3-Clause No Details →
17.0.0-rc10 03 Nov 2017 H1 BSD-3-Clause No Details →
17.0.0-rc9 22 Oct 2017 H1 BSD-3-Clause No Details →
17.0.0-rc8 18 Oct 2017 H1 BSD-3-Clause No Details →
17.0.0-rc6 07 Oct 2017 H1 BSD-3-Clause No Details →
17.0.0-rc4 06 Oct 2017 H1 BSD-3-Clause No Details →
17.0.0-rc3 06 Oct 2017 H1 BSD-3-Clause No Details →
17.0.0-rc2 02 Oct 2017 H1 BSD-3-Clause No Details →
17.0.0-rc1 28 Sep 2017 H1 BSD-3-Clause No Details →
16.6.2 25 Sep 2017 H1 BSD-3-Clause No Details →
16.6.1 24 Sep 2017 H1 BSD-3-Clause No Details →
16.6.0 12 Sep 2017 H1 BSD-3-Clause No Details →
16.5.2 04 Aug 2017 H1 BSD-3-Clause No Details →
16.5.1 04 Aug 2017 H1 BSD-3-Clause No Details →
16.5.0 20 Jul 2017 H1 BSD-3-Clause No Details →
16.4.3 09 Jun 2017 H1 BSD-3-Clause No Details →
16.4.2 08 Jun 2017 H1 BSD-3-Clause No Details →
16.4.1 05 Jun 2017 H1 BSD-3-Clause No Details →
16.4.0 05 Jun 2017 H1 BSD-3-Clause No Details →
16.3.1 05 Jun 2017 H1 BSD-3-Clause No Details →
16.3.0 30 May 2017 H1 BSD-3-Clause No Details →
16.2.0 29 May 2017 H1 BSD-3-Clause No Details →
16.1.1 31 Mar 2017 H1 BSD-3-Clause No Details →
16.1.0 29 Dec 2016 H2 BSD-3-Clause No Details →
16.0.3 29 Dec 2016 H2 BSD-3-Clause No Details →
16.0.2 19 Dec 2016 H2 BSD-3-Clause No Details →
16.0.1 01 Dec 2016 H2 BSD-3-Clause No Details →
16.0.0 30 Nov 2016 H2 BSD-3-Clause No Details →
15.2.0 20 Oct 2016 H2 BSD-3-Clause No Details →
15.1.1 27 Sep 2016 H2 BSD-3-Clause No Details →
15.1.0 27 Sep 2016 H2 BSD-3-Clause No Details →
15.0.3 01 Sep 2016 H2 BSD-3-Clause No Details →
15.0.2 28 Aug 2016 H2 BSD-3-Clause No Details →
15.0.1 26 Aug 2016 H2 BSD-3-Clause No Details →
14.2.0 13 Aug 2016 H1 BSD-3-Clause No Details →
14.1.0 01 Aug 2016 H1 BSD-3-Clause No Details →
13.5.3 29 Jul 2016 H1 BSD-3-Clause No Details →
14.0.0 29 Jul 2016 H1 BSD-3-Clause No Details →
13.5.0 06 Jul 2016 H1 BSD-3-Clause No Details →
13.4.2 04 Jul 2016 H1 BSD-3-Clause No Details →
13.4.1 21 May 2016 H1 BSD-3-Clause No Details →
13.4.0 07 May 2016 H1 BSD-3-Clause No Details →
13.3.0 02 Apr 2016 H1 BSD-3-Clause No Details →
13.2.2 25 Mar 2016 H1 BSD-3-Clause No Details →
13.2.1 11 Mar 2016 H1 BSD-3-Clause No Details →
13.2.0 11 Mar 2016 H1 BSD-3-Clause No Details →
13.1.0 10 Mar 2016 H1 BSD-3-Clause No Details →
13.0.0 01 Feb 2016 H1 BSD-3-Clause No Details →
9.5.1 20 Jan 2016 H2 M2 BSD-3-Clause No Details →
12.1.0 09 Jan 2016 H1 BSD-3-Clause No Details →
12.0.1 06 Jan 2016 H1 BSD-3-Clause No Details →
12.0.0 04 Jan 2016 H1 BSD-3-Clause No Details →
11.1.4 27 Dec 2015 H1 BSD-3-Clause No Details →
11.1.3 23 Dec 2015 H1 M1 BSD-3-Clause No Details →
11.1.2 21 Nov 2015 H2 M1 BSD-3-Clause No Details →
11.1.1 14 Nov 2015 H2 M1 BSD-3-Clause No Details →
11.1.0 05 Nov 2015 H2 M1 BSD-3-Clause No Details →
11.0.5 03 Nov 2015 H2 M1 BSD-3-Clause No Details →
11.0.4 03 Nov 2015 H2 M1 BSD-3-Clause No Details →
11.0.3 30 Oct 2015 H2 M1 BSD-3-Clause No Details →
11.0.2 21 Oct 2015 H2 M1 BSD-3-Clause No Details →
11.0.1 20 Oct 2015 H2 M1 BSD-3-Clause No Details →
11.0.0 16 Oct 2015 H2 M1 BSD-3-Clause No Details →
10.5.0 15 Oct 2015 H2 M2 — No Details →
10.4.1 08 Oct 2015 H2 M2 — No Details →
10.4.0 05 Oct 2015 H2 M2 — No Details →
10.2.1 03 Oct 2015 H2 M2 — No Details →
10.1.0 25 Sep 2015 H2 M2 — No Details →
10.0.1 23 Sep 2015 H2 M2 — No Details →
10.0.0 11 Sep 2015 H2 M2 — No Details →
9.3.1 08 Sep 2015 H2 M2 — No Details →
9.3.0 06 Sep 2015 H2 M2 — No Details →
9.2.0 05 Sep 2015 H2 M2 — No Details →
9.1.0 04 Sep 2015 H2 M2 — No Details →
9.0.4 02 Sep 2015 H2 M2 — No Details →
9.0.3 19 Aug 2015 H2 M2 — No Details →
9.0.2 15 Aug 2015 H2 M2 — No Details →
9.0.1 12 Aug 2015 H2 M2 — No Details →
9.0.0 12 Aug 2015 H2 M2 — No Details →
8.8.1 29 Jul 2015 H2 M2 — No Details →
8.8.0 03 Jul 2015 H2 M2 — No Details →
8.6.1 05 Jun 2015 H2 M2 — No Details →
8.6.0 29 May 2015 H2 M2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 3
  • 2020 3

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

03 Vulnerabilities

Recorded vulnerabilities for hapi

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16013: Denial of Service via malformed accept-encoding header in hapi 7.5 high 16.1.1 09 Oct 2018
CVE-2014-4671: Rosetta-Flash JSONP Vulnerability in hapi N/A medium 6.1.0 31 Aug 2020
Denial of Service in hapi N/A high No fix published 03 Sep 2020
CVE-2014-3742: File Descriptor Leak Can Cause DoS Vulnerability in hapi N/A high 2.2.0 24 Oct 2017
CVE-2015-9243: Unsafe Merging of CORS Configuration Conflict in hapi N/A medium 11.1.4 01 Sep 2020

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 hapi

Is hapi safe to use?

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

What is hapi's Vulert package health score?

Vulert scores hapi 45/100, which reads as risky. 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 registry marks the latest release as deprecated, which caps this score.

Is the latest version of hapi affected?

Yes. 18.1.0, 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.

Which version of hapi should I use?

18.1.0 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 hapi have?

7 vulnerabilities are recorded for hapi in the npm ecosystem: 0 critical, 4 high, 3 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 hapi vulnerabilities disclosed?

0 vulnerabilities were recorded for hapi in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 hapi 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 hapi for upcoming vulnerabilities?

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