Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-93671Published 2026-11-16

CVE-2026-93671 — zephyrproject zephyr

low

As of 2026-11-17, CVE-2026-93671 is a LOW-severity vulnerability in zephyrproject zephyr, CVSS v3.1 3.7, EPSS 0.1% (9.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-93671 as of 2026-11-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
3.7/10Low
EPSS
0.1%Higher than 9.4% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
2.2/10Threadlinqs triage score
Published
Updated 2026-11-17
CVSS v3.1 3.7 (LOW) · EPSS 0.1% (higher than 9.4% of all scored CVEs) · Priority 2.2/10 · Published 2026-11-16

Last updated:

What is CVE-2026-93671?

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.

The record classifies CVE-2026-93671 under weakness class CWE-125. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.

Severity and exploitation probability

CVSS v3.1 base score
3.7 — LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 9.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
2.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-11-16

Is CVE-2026-93671 being exploited?

It currently carries a trending score of 32 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-93671

Patch reference: https://github.com/zephyrproject-rtos/zephyr/commit/221b72b32060e613ee5f2416b270073d7be79277. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-93671

No threat campaign in the Threadlinqs corpus currently references CVE-2026-93671, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references