CVE-2026-48049

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 80% 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: cna:github_m, epss
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

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

@hapi/inert has a static-file confinement bypass via sibling-prefix path

Impact

@hapi/inert serves static files from a directory configured with path (in the directory / file handlers) or relativeTo (for h.file()), with confinement enforced by the confine option (default true). Before the patch, the confinement check compared the resolved absolute path against the confine directory using a raw string-prefix test, so a sibling directory whose absolute path begins with the same characters as the confine directory (eg. /app/static-secret next to a served /app/static) was incorrectly accepted as confined. An unauthenticated remote attacker who knows or guesses such a sibling name can read any file inside it via a request like /..%2fstatic-secret/secret.txt, provided the file is readable by the server process. Only applications that happen to have a sibling directory sharing a string prefix with the served directory are exploitable; applications with no such sibling are unaffected.

Patches

Upgrade to 7.1.1.

Workarounds

For users who cannot upgrade immediately: ensure the directory served via inert has no sibling whose name starts with the same characters (for example, rename static-secret/ to secret/, or move it to a different parent directory).

Resources

Pull Request: https://github.com/hapijs/inert/pull/176

CVSS v3
5.3
EG Score
5.3(low)
EPSS
19.6%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 11, 2026

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—

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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-07 02:52 UTCEG score recompute
  2. 2026-07-05 11:04 UTCEG score recompute
  3. 2026-07-04 11:23 UTCEG score recompute
  4. 2026-07-03 08:33 UTCEG score recompute
  5. 2026-07-02 10:05 UTCEG score recompute
  6. 2026-07-01 11:51 UTCEG score recompute
  7. 2026-06-30 13:38 UTCEG score recompute
  8. 2026-06-29 13:47 UTCEG score recompute
  9. 2026-06-28 15:34 UTCEG score recompute
  10. 2026-06-27 17:20 UTCEG score recompute
  11. 2026-06-26 19:08 UTCEG score recompute
  12. 2026-06-25 20:54 UTCEG score recompute
  13. 2026-06-24 22:41 UTCEG score recompute
  14. 2026-06-24 00:29 UTCEG score recompute
  15. 2026-06-23 02:13 UTCEG score recompute
  16. 2026-06-22 04:00 UTCEG score recompute
  17. 2026-06-21 02:24 UTCEG score recompute
  18. 2026-06-20 04:00 UTCEG score recompute
  19. 2026-06-19 05:23 UTCEG score recompute
  20. 2026-06-18 07:03 UTCEG score recompute
  21. 2026-06-17 07:25 UTCEG score recompute
  22. 2026-06-16 09:04 UTCEG score recompute
  23. 2026-06-15 10:50 UTCEG score recompute
  24. 2026-06-14 23:18 UTCEPSS rescore
  25. 2026-06-14 12:35 UTCEG score recompute
Show 5 more
  1. 2026-06-13 23:00 UTCEPSS rescore
  2. 2026-06-13 14:22 UTCEG score recompute
  3. 2026-06-12 23:12 UTCEPSS rescore
  4. 2026-06-12 16:10 UTCEG score recompute
  5. 2026-06-11 17:56 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48049?
CVE-2026-48049 is a medium vulnerability published on June 11, 2026. @hapi/inert has a static-file confinement bypass via sibling-prefix path Impact @hapi/inert serves static files from a directory configured with path (in the directory / file handlers) or relativeTo (for h.file()), with confinement enforced by the confine option (default true). Before the patch,…
When was CVE-2026-48049 disclosed?
CVE-2026-48049 was first published in the National Vulnerability Database on June 11, 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 19.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48049?
CVE-2026-48049 has a CVSS v4.0 base score of 5.3 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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