boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-18746

zephyrproject zephyr — NULL pointer dereference in Zephyr LwM2M client when the CoAP Block1 context pool is exhausted
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   N   H   N   N  U  N  N  H    5.9   .0026   18.5     —
AFFECTED
  Product  Versions  Fixed
  zephyr   3.7.0 –   —
TIMELINE
  Aug 3   Reserved by zephyr
  Sep 28  Published (CNA: zephyr)
  Nov 6   EXPLOIT PUBLISHED — CVE-2026-18746 (zephyrproject zephyr). Public exploit reference added.
CWE-476 · CNA: zephyr · CVSS v3.1 · 2 references · NVD status: Analyzed

Description

parse_write_op() in subsys/net/lib/lwm2m/lwm2m_message_handling.c handles inbound CoAP WRITE/CREATE requests that carry a Block1 option. For the first block of a transfer it called init_block_ctx() and then immediately stored the peer-selected block size with block_ctx->ctx.block_size = block_size before inspecting the return code. init_block_ctx() sets the caller's pointer to NULL and returns -ENOMEM when no entry of the static block1_contexts[] pool is free or timed out, so that store dereferences a NULL pointer. The pool holds CONFIG_LWM2M_NUM_BLOCK1_CONTEXT entries (default 3) and an entry is only reclaimed once its transfer completes, fails, or ages past 30 seconds. A peer that reaches the client's LwM2M socket can therefore start three block-wise writes on three distinct object paths with the CoAP More bit set and leave them incomplete, then send the first block of a fourth write on a new path to reach the unguarded dereference. Reachability is gated only by the connected UDP socket's source-address filter unless CONFIG_LWM2M_DTLS_SUPPORT is enabled — which has no default — so in a NoSec deployment an on-path or address-spoofing attacker needs no credentials; the same sequence is also reachable from a bootstrap or lower-trust server, and can be hit accidentally by a legitimate server running four concurrent block transfers. The write targets a fixed low address with a value between 0 and 7, so the consequence is a fatal memory fault (BusFault or corrupted low memory leading to a fault) rather than a usable memory-corruption primitive: the device crashes or resets. Confidentiality and integrity are not affected. The fix moves the store below the guard and validates the context pointer itself instead of the return code, so the context is only touched once it is known to be valid.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
August 3, 2026ReservedReserved by zephyr
September 28, 2026PublishedPublished (CNA: zephyr)
November 6, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2026-18746 (zephyrproject zephyr). Public exploit reference added.

Affected

Affected products and packages — 1 row
VendorProduct / PackageEcosystemVersion introducedFixed
zephyrprojectzephyr—3.7.0—

Weaknesses

CWE-476

References (2)

Related

Authoritative record: CVE-2026-18746 at cve.org

Vendors: zephyrproject

Weaknesses: CWE-476

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-18746 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.