CVE-2026-10672
LwM2M firmware-update URI buffer bug leads to info disclosure and device crash.
Is CVE-2026-10672 being exploited?
Not confirmed. CVE-2026-10672 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-10672?
CVE-2026-10672 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-10672?
Yes. A fix has been recorded for CVE-2026-10672. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-10672 affect?
CVE-2026-10672 affects Zephyr RTOS subsys/net/lib/lwm2m v3.0.0 through v4.4.0, Devices with CONFIG_LWM2M_FIRMWARE_UPDATE_PULL_SUPPORT enabled, LwM2M clients using Firmware-Update object (/5/0/1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-10672?
Apply Zephyr patch/update; enforce DTLS and restrict trusted LwM2M servers.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker or malicious LwM2M server can leak adjacent device memory and crash device (DoS) via crafted Package URI; may expose secrets.
Patch when possible
- affected>= 3.0.0 and < 4.5.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.