| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-rcvq-m9j9-6f4g | @hapi/inert has a static-file confinement bypass via sibling-prefix path |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 28 Jul 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hapi
Hapi inert |
|
| Vendors & Products |
Hapi
Hapi inert |
Tue, 21 Jul 2026 03:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 17 Jul 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | @hapi/inert: Static-file confinement bypass via sibling-prefix path | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-07-21T02:26:04.404Z
Reserved: 2026-05-20T18:15:53.578Z
Link: CVE-2026-48049
Updated: 2026-07-21T02:25:58.780Z
Status : Deferred
Published: 2026-07-17T22:17:14.557
Modified: 2026-07-23T16:10:54.923
Link: CVE-2026-48049
No data.
OpenCVE Enrichment
Updated: 2026-07-30T23:30:08Z
Github GHSA