Medium, CVSS 5.3npmAmendedPublished
@hapi/inert has a static-file confinement bypass via sibling-prefix path
CVE-2026-48049 · GHSA-rcvq-m9j9-6f4g
- Affected
- npm @hapi/inert >= 4.0.0, <= 7.1.0
- Fixed in
- 7.1.1· Vendor fix available
- Issue
- Impact @hapi/inert serves static files from a directory configured with path (in the directory / file handlers) or relativeTo (for h.file()), with confinement enforced by the confine option (default true). Before the patch, the confinement check compared the resolved absolute path against the confine directory using a raw string-prefix test, so a sibling directory whose absolute path begins with the same characters as the confine directory (eg. /app/static-secret next to a served /app/static) was incorrectly accepted as confined. An unauthenticated remote attacker who knows or guesses such a sibling name can read any file inside it via a request like /..%2fstatic-secret/secret.txt, provided the file is readable by the server process. Only applications that happen to have a sibling directory sharing a string prefix with the served directory are exploitable; applications with no such sibling are unaffected. Patches Upgrade to 7.1.1. Workarounds For users who cannot upgrade immediately:…
Recommended action: Upgrade to 7.1.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.