Denial of Service in hapi

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2015-9241: 2.10% estimated exploitation activity in the next 30 days; percentile 81.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Versions of hapi prior to 11.1.3 are affected by a denial of service vulnerability. The vulnerability is triggered when certain input is passed into the If-Modified-Since or Last-Modified headers. This causes an 'illegal access' exception to be raised, and instead of sending a HTTP 500 error back to the sender, hapi will continue to hold the socket open until timed out (default node timeout is 2 minutes). Recommendation Update to v11.1.3 or later

Published by the source

7 Jun 2018, 19:43 UTC

Last modified by the source

8 Nov 2023, 03:58 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rc8h-3fv6-pxv8

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rc8h-3fv6-pxv8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2015-9241

Advisory: Denial of Service in hapi
IDs: CVE-2015-9241, GHSA-rc8h-3fv6-pxv8
Record: https://patchnext.com/advisories/cve-2015-9241 (revision 2, source checked 26 Oct 2026, 12:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hapi 11.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm hapi: affected < 11.1.3; fixed in 11.1.3

## Suggested inspection (read-only)
- `npm ls hapi --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hapi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rc8h-3fv6-pxv8 (OSV record GHSA-rc8h-3fv6-pxv8 lists affected ranges: npm hapi >=0 <11.1.3 (fixed))
- Verified: https://github.com/advisories/GHSA-rc8h-3fv6-pxv8 (GitHub-reviewed advisory GHSA-rc8h-3fv6-pxv8 lists affected ranges: npm hapi >=0 <11.1.3)

Commands are suggestions: review each one before running it.