Skip to content

CVE-2026-48049 @hapi/inert: Static-file confinement bypass via sibling-prefix path

MediumCVSS 5.3 EPSS 0.59%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: yes · technical impact: partial

Description

@hapi/inert provides static file and directory handlers for hapi.js. From 4.0.0 to 7.1.0, @hapi/inert serves static files from a directory configured with path in the directory or file handlers or relativeTo for h.file(), with confinement enforced by the confine option, but the confinement check compared the resolved absolute path against the confine directory using a raw string-prefix test, so a sibling directory such as /app/static-secret next to /app/static was incorrectly accepted and could allow an unauthenticated remote attacker to read files via /..%2fstatic-secret/secret.txt. This issue is fixed in version 7.1.1.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
hapi inert(npm) >= 4.0.0, < 7.1.1; >= 4.0.0, <= 7.1.0 7.1.1 Fixed
hapijs inert = >= 4.0.0, < 7.1.1 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
hapijs inert = >= 4.0.0, < 7.1.1 No fix listed
hapi inert(npm) >= 4.0.0, <= 7.1.0 No fix listed
hapi inert(npm) >= 4.0.0, < 7.1.1 7.1.1

References