CVE-2026-8023

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 /<prefix>/../../<file> is dispatched to the handler and, after the underlying filesystem (e.g. LittleFS/FAT) resolves the .. segments, escapes the configured web root, letting an unauthenticated remote client read arbitrary readable files on the mounted volume (information disclosure). The HTTP server requires no TLS or authentication to reach this path. The fix adds http_server_remove_dot_segments(), which canonicalizes the path portion of the URL before resource lookup in both protocol handlers, neutralizing the traversal. Affects releases v4.0.0 through v4.4.0 for deployments that register a static-filesystem resource.

• CWE-22
• CWE-23
• CWE-22

• https://github.com/zephyrproject-rtos/zephyr/commit/f4a423c98554f209c5d2f22f041822422c9263b8Patch
• https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-hch3-53g6-jj3hExploit, Patch, Vendor Advisory
• https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-hch3-53g6-jj3hExploit, Patch, Vendor Advisory

Published

Jun 29, 2026

Last Modified

Jul 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-8017Side-channel information leakage in Media in Google Chrome p…3.1
• CVE-2026-8018Insufficient policy enforcement in DevTools in Google Chrome…8.1
• CVE-2026-8019Insufficient policy enforcement in WebApp in Google Chrome p…5.4
• CVE-2026-8020Uninitialized Use in GPU in Google Chrome on Android prior t…5.3
• CVE-2026-8021Script injection in UI in Google Chrome prior to 148.0.7778.…4.2
• CVE-2026-8022Inappropriate implementation in MHTML in Google Chrome prior…3.1
• CVE-2026-8024A remote, unauthenticated attacker may exploit a deserializa…9.8
• CVE-2026-8025Improper neutralization of special elements used in an SQL c…9.8
• CVE-2026-8026A security flaw has been discovered in FlowiseAI Flowise up …5.3
• CVE-2026-8027A weakness has been identified in FlowiseAI Flowise up to 3.…5.3
• CVE-2026-8028A vulnerability was detected in FlowiseAI Flowise up to 3.0.…3.7
• CVE-2026-8029The ZTE Smart Life app contains an SQL injection vulnerabili…3.9