CVE-2026-48049

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

@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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

June 11, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
Patch available. Sources: github, github_pr, github_commit.
github_commit

commit bcceb761a43b (hapijs/inert)

Fix landed in hapijs/inert commit bcceb761a43b — awaiting tagged release

https://github.com/hapijs/inert/commit/bcceb761a43b9d1178eb6bd553e4ad2bb70494d9
github_pr

fix: block sibling-prefix path traversal

Fix merged in hapijs/inert PR #176 on 2026-05-20 — awaiting tagged release

https://github.com/hapijs/inert/pull/176
github Patch Available

Static-file confinement bypass via sibling-prefix path · Advisory · hapijs/inert · GitHub

https://github.com/hapijs/inert/security/advisories/GHSA-rcvq-m9j9-6f4g

Vendor Advisories for CVE-2026-48049(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@hapi/inert—7.1.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 05:16 UTCEG score recompute
  3. 2026-07-25 14:18 UTCEPSS rescore
  4. 2026-07-24 14:18 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:18 UTCEG score recompute
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:24 UTCEPSS rescore
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 02:29 UTCEPSS rescore
  12. 2026-06-14 23:18 UTCEPSS rescore
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-11 17:56 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48049?
CVE-2026-48049 is a medium vulnerability published on June 11, 2026. @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…
When was CVE-2026-48049 disclosed?
CVE-2026-48049 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48049 actively exploited?
CVE-2026-48049 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.5% of all scored CVEs.
What is the CVSS score of CVE-2026-48049?
CVE-2026-48049 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-48049?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48049, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48049

Explore →

Is Your Infrastructure Affected by CVE-2026-48049?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs