CVE-2026-8023 - Zephyr's HTTP server (subsys/net/lib/http) provides a static-filesystem resource type (HTTP_RESOURCE_TYPE_STAT

CVE-2026-8023 + Zephyr’s HTTP server (subsys/net/lib/http) provides a static-filesystem resource type (HTTP_RESOURCE_TYPE_STAT + High + 2026-06-29

One-sentence business risk

Attackers can turn a normal application path into code execution, making this a direct production-host takeover risk.

Research notes

  • Root cause: 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.
  • Affected versions: 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_ur.
  • Fixed / safe versions: patched to the handler and.
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Exact vulnerable code pattern

run("tool " + user_controlled_value)

Fixed / mitigated code pattern

run(["tool", user_controlled_value], shell=False) with an allowlisted argument schema

Dependency or runtime update:

rg -n "wolfssl|OpenSSL|X509|ML-KEM|X25519" .
# update vendored library/submodule/package to the fixed vendor release and rebuild

Step-by-step integration guide

  1. Inventory affected component across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to patched to the handler and or apply the exact vendor patch referenced below.
  3. Replace the vulnerable command-injection pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-8023-zephyr-s-http-server-subsys-net-lib-http-provide
source: NVD bulk JSON feed
dependency_or_product: "affected component"
affected: "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_ur"
fixed: "patched to the handler and"
signals:
  - "command-injection"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-8023 (Zephyr's HTTP server (subsys/net/lib/http) provides a static-filesystem resource type (HTTP_RESOURCE_TYPE_STAT) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to patched to the handler and. Replace the vulnerable command-injection pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-8023, command-injection, affected component, NVD bulk JSON feed.
  • Affected tech stack: c/c++.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, high_priority_sla.

References