Skip to main content
Menu
CVEs

CVE

Zephyr out-of-bounds read in WebSocket client handshake

CVE-2026-93671EUVD-2026-126669

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

3.7LowCNA
Exploited
No known exploitation
Fix
Fixed in 4.3.2, 4.5.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.3.2, 4.5.0.

Published
Last modified
Reference
Last checked
21/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The Zephyr WebSocket client can read past the end of its receive buffer when it logs a mismatched Sec-WebSocket-Accept header, and a remote server can trigger this during the handshake without logging in. An attacker can use this to expose adjacent memory in the device's logs, or to crash the connection or thread where the memory after the buffer is unmapped.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

The websocket client's HTTP header callback on_header_value() in subsys/net/lib/websocket/websocket.c receives the Sec-WebSocket-Accept header value as a pointer/length pair from the HTTP parser. The referenced bytes live inside the application-supplied receive buffer and are not NUL terminated. When the received value did not match the expected accept key, the pointer was passed directly to a %s conversion in a NET_DBG() call, so the logging code measured the string with strlen() and read on past the end of the header value looking for a terminator.

The value is supplied by the peer during the WebSocket handshake, before any application-level authentication, so a malicious or man-in-the-middle server reached over a ws:// (or otherwise attacker-terminated) connection can trigger the mismatch branch at will simply by answering with a wrong accept key. By sizing the response so the header value ends at the tail of the buffer passed to websocket_connect() as wreq->tmp_buf, the peer can make the scan run off the end of that buffer and into adjacent memory. The defective log statement is compiled in only when websocket debug logging is enabled (CONFIG_NET_WEBSOCKET_LOG_LEVEL_DBG=y, or CONFIG_LOG_DEFAULT_LEVEL=4); it is absent from a default build, which bounds exposure to diagnostic configurations.

The consequence is an out-of-bounds read whose contents are emitted to the log stream: memory adjacent to the receive buffer is disclosed wherever the device's logs are collected or displayed. On targets where the memory following the buffer is not mapped, the scan can instead fault and terminate the connection or thread. No out-of-bounds write occurs, so there is no integrity impact.

The fix copies at most sizeof(got) - 1 bytes of the parser-provided slice into a bounded stack buffer, NUL terminates the copy, and logs that instead, so the formatter never reads beyond the bytes the parser actually offered.

cve.now Index

21Pcve.now Index 21 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity3.7/10CVSS 3.7
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 26 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.3.2, 4.5.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-93671 (Out-of-bounds read logging a mismatched Sec-WebSocket-Accept header in the Zephyr websocket client), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-93671 (entry last updated 2026-11-16):
Affected:
- zephyrproject zephyr: from 2.1.0, fixed in 4.3.2; from 4.4.0, fixed in 4.5.0
Fixed versions: 4.3.2, 4.5.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-93671 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-93671 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/zephyrproject-rtos/zephyr/commit/221b72b32060e613ee5f2416b270073d7be79277
- https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-686p-f363-q695
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-93671
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-93671"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • zephyr

    From 2.1.0 · fixed in 4.3.2; From 4.4.0 · fixed in 4.5.0

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-93671

Is CVE-2026-93671 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-93671?

zephyr: from 2.1.0 before 4.3.2; from 4.4.0 before 4.5.0.Source: cve.now feed data

How do I fix CVE-2026-93671?

Upgrade to a fixed version: 4.3.2, 4.5.0.Source: cve.now feed data