Approved changes feed: RSS · Atom
cpe:2.3:a:hapijs:inert:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Hapijs (cde07e56-6e3e-5211-9d96-925613bfc13f) |
|---|---|
| Product | Inert (2ff26310-f1b4-5867-9f4b-f7b015ff2dd1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-48049 |
vulnerable | 2026-07-29 00:55:01.051054 |
@hapi/inert: Static-file confinement bypass via sibling-prefix path
MEDIUM (5.3)
@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.
Published: 2026-07-17T21:03:16.577Z
Updated: 2026-07-21T02:26:04.404Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.