CVE-2026-93671: zephyrproject zephyr · Bounds
Affects zephyrproject zephyrSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 4.5.0 or 4.3.2 when convenient.
Data as of 16 Nov 2026, 21:36 UTC
Thin evidence
One scorer or none| CNA (zephyr) | CVSS 3.1 | 3.7 |
|---|
- Patch
- Available – fixed in 4.5.0, 4.3.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade zephyrproject zephyr to 4.5.0 or 4.3.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| zephyrprojectzephyr | Affected
| Fixed in
|
| zephyrprojectzephyr | Affected
| Fixed in
|
GitHubzephyrpkg:github/zephyrOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Zephyr versions 4.3.2 or 4.5.0 or later where the issue is fixed. The fix involves copying the header value into a bounded, NUL-terminated buffer before logging to prevent out-of-bounds reads. If upgrading is not immediately possible, disabling websocket debug logging (CONFIG_NET_WEBSOCKET_LOG_LEVEL_DBG=y or CONFIG_LOG_DEFAULT_LEVEL=4) will prevent the vulnerable log code from being compiled and executed, mitigating the issue.
Description
CVE-2026-93671 is a low-severity vulnerability in the Zephyr project's websocket client. It involves an out-of-bounds read in the HTTP header callback during WebSocket handshake logging when debug logging is enabled. A malicious server can trigger this by sending a malformed Sec-WebSocket-Accept header, causing adjacent memory to be read and logged. This does not affect integrity or availability but can disclose memory contents in logs. The issue is fixed in Zephyr versions 4.3.2 and 4.5.0.