CVE-2026-48049
@hapi/inert provides static file and directory handlers for …
@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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/hapijs/inert/security/advisories/GHSA-rcvq-m9j9-6f4g
- github.com/hapijs/inert/pull/176
- github.com/hapijs/inert/commit/a65e5b271b5c3405af463469959c5e052eb23a62
- github.com/advisories/GHSA-rcvq-m9j9-6f4g
- github.com/hapijs/inert/commit/bcceb761a43b9d1178eb6bd553e4ad2bb70494d9
- github.com/hapijs/inert/releases/tag/v7.1.1
- nvd.nist.gov/vuln/detail/CVE-2026-48049
- cve.org/CVERecord?id=CVE-2026-48049
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.