Is hapi 10.2 vulnerable?

npm · 1 release from 10.2.1 to 10.2.1 · latest hapi is 18.1.0 · checked 2 Nov 2026

Yes: 4 known advisories

Yes. hapi 10.2.1, the last 10.2 release, is affected by 4 known security advisories (2 high, 2 medium), including CVE-2015-9241, CVE-2015-9243, CVE-2015-9236. At least one has no fixed release yet.

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting hapi 10.2.1

  • HighGHSA-7hx8-2rxv-66xv3 Sept 2020

    Denial of Service in hapi

    Affected
    >=0.0.0
    Fixed in
    No fix released
  • MediumCVE-2015-9243GHSA-j3g2-m5jj-63361 Sept 2020

    Unsafe Merging of CORS Configuration Conflict in hapi

    Affected
    <11.1.4
    Fixed in
    11.1.4
  • MediumCVE-2015-9236GHSA-vwrf-r5r4-77757 Jun 2018

    Incorrect handling of CORS preflight request headers in hapi

    Affected
    <11.0.0
    Fixed in
    11.0.0
  • HighCVE-2015-9241GHSA-rc8h-3fv6-pxv87 Jun 2018

    Denial of Service in hapi

    Affected
    <11.1.3
    Fixed in
    11.1.3

Which of your client projects are still on hapi 10.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact hapi version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other hapi versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.