CVE-2026-48049 @hapi/inert: Static-file confinement bypass via sibling-prefix path
- 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.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| 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
| Product | Affected versions | Fixed 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
- https://github.com/hapijs/inert/security/advisories/GHSA-rcvq-m9j9-6f4g vendor-advisory
- https://github.com/hapijs/inert/pull/176 patch
- https://github.com/hapijs/inert/commit/bcceb761a43b9d1178eb6bd553e4ad2bb70494d9
- https://github.com/hapijs/inert/releases/tag/v7.1.1
- github.com patch
- github.com
- github.com product