Zephyr's HTTP server (subsys/net/lib/http) provides a static-filesystem resource type (HTTP_RESOURCE_TYPE_STATIC_FS, available when CONFIG_FILE_SYSTEM is enabled) that serves files from a configured root directory. Before this fix, both the HTTP/1 and HTTP/2 front-ends placed the raw, attacker-controlled request path into client-url_buffer (assembled in on_url() for HTTP/1 and copied verbatim from the :path pseudo-header for HTTP/2) without resolving ./.. segments. The static-FS handler then built the on-disk filename by directly concatenating the configured root with that raw URL (snprintk(fname, ..., "%s%s", static_fs_detail-fs_path, client-url_buffer) at http_server_http1.c:603 and http_server_http2.c:490) and opened it with fs_open(fname, FS_O_READ). Because the handler is reached via wildcard/leading-dir (fnmatch FNM_LEADING_DIR) or fallback resource matching, a request such as GET /
CVE-2026-8023
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 44% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 55.8%
- KEV
- Not listed
Published
June 29, 2026
Last Modified
July 6, 2026
Advisory Details (2)
Auto-updated Jun 30, 2026Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') · Advisory · zephyrproject-rtos/zephyr · GitHub
https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-hch3-53g6-jj3hcommit f4a423c98554 (zephyrproject-rtos/zephyr)
Fix landed in zephyrproject-rtos/zephyr commit f4a423c98554 — awaiting tagged release
https://github.com/zephyrproject-rtos/zephyr/commit/f4a423c98554f209c5d2f22f041822422c9263b8Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 43× 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.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 00:53 UTCEG score recompute
- 2026-07-11 12:48 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 00:43 UTCEG score recompute
- 2026-07-10 12:36 UTCEG score recompute
- 2026-07-10 00:30 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 12:21 UTCEG score recompute
- 2026-07-09 00:16 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 12:11 UTCEG score recompute
- 2026-07-08 00:03 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 11:58 UTCEG score recompute
- 2026-07-06 23:53 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 11:43 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:35 UTCEG score recompute
- 2026-07-05 11:30 UTCEG score recompute
Show 18 moreShow fewer
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 23:24 UTCEG score recompute
- 2026-07-04 11:19 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 23:14 UTCEG score recompute
- 2026-07-03 11:06 UTCEG score recompute
- 2026-07-02 22:59 UTCEG score recompute
- 2026-07-02 10:54 UTCEG score recompute
- 2026-07-01 22:46 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 10:42 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 22:36 UTCEG score recompute
- 2026-06-30 10:31 UTCEG score recompute
- 2026-06-29 22:25 UTCEG score recompute
- 2026-06-29 22:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-8023?
When was CVE-2026-8023 disclosed?
Is CVE-2026-8023 actively exploited?
What is the CVSS score of CVE-2026-8023?
How do I remediate CVE-2026-8023?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-8023
Is Your Infrastructure Affected by CVE-2026-8023?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.