CVE-2026-10672

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
9.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

subsys/net/lib/lwm2m/lwm2m_pull_context.c copied the firmware-update Package URI into a fixed static buffer (context.uri, size CONFIG_LWM2M_SWMGMT_PACKAGE_URI_LEN, default 128) with memcpy(context.uri, uri, LWM2M_PACKAGE_URI_LEN), copying exactly the destination size with no length validation. The Firmware-Update object stores the server-supplied Package URI (/5/0/1) in a 255-byte buffer, so a LwM2M management server (or an on-path attacker on a session lacking strong DTLS) can WRITE a URI of 128-254 characters; only the first 128 bytes are then copied into context.uri with no NUL terminator. That buffer is subsequently consumed as a C string by http_parser_parse_url(context.uri, strlen(context.uri), ...), strlen-based CoAP URI-path/PROXY-URI option appends, and lwm2m_parse_peerinfo(), causing an out-of-bounds read of adjacent static memory. The over-read bytes are appended to outbound CoAP requests (information disclosure of adjacent device memory to the server/proxy) and can crash the device (denial of service). The vulnerable copy was introduced by the pull-context refactor (first released in v3.0.0) and is present through v4.4.0; the default-on CONFIG_LWM2M_FIRMWARE_UPDATE_PULL_SUPPORT path is affected. The fix adds a strlen(uri) >= sizeof(context.uri) check returning -ENOMEM and switches to strcpy(), guaranteeing a bounded, NUL-terminated buffer.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

August 6, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Remote out-of-bounds read in LwM2M firmware pull URI handling · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-rf6j-4mpp-j9mf
GitHub commit

commit 99a164df5cea (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 99a164df5cea — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/99a164df5cea5af76e32b57c6d51854f018969a2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 131 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 31 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 09:51 UTCEG score recompute
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-12 16:39 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-11 20:14 UTCEG score recompute
  6. 2026-10-11 18:26 UTCEG score recompute
  7. 2026-10-11 15:00 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-01 13:24 UTCEG score recompute
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-09-28 09:22 UTCEG score recompute
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-09-24 09:54 UTCEG score recompute
  25. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 75 more
  1. 2026-09-23 03:56 UTCEG score recompute
  2. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-09-18 04:55 UTCEG score recompute
  5. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-09-13 23:28 UTCEG score recompute
  7. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-09-13 07:55 UTCEG score recompute
  9. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-09-12 01:46 UTCEG score recompute
  11. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-09-08 01:46 UTCEG score recompute
  16. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-09-06 17:52 UTCEG score recompute
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-09-05 21:18 UTCEG score recompute
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-08-30 20:25 UTCEG score recompute
  25. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-08-30 05:24 UTCEG score recompute
  27. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-08-27 21:34 UTCEG score recompute
  30. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  31. 2026-08-26 23:58 UTCEG score recompute
  32. 2026-08-25 19:12 UTCEG score recompute
  33. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-08-24 19:50 UTCEG score recompute
  35. 2026-08-24 09:45 UTCEG score recompute
  36. 2026-08-23 01:02 UTCEG score recompute
  37. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-08-22 00:01 UTCEG score recompute
  39. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  40. 2026-08-21 02:59 UTCEG score recompute
  41. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-08-20 00:34 UTCEG score recompute
  43. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-08-18 20:06 UTCEG score recompute
  45. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-08-17 14:51 UTCEG score recompute
  47. 2026-08-16 18:33 UTCEG score recompute
  48. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  49. 2026-08-16 02:18 UTCEG score recompute
  50. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  51. 2026-08-15 01:55 UTCEG score recompute
  52. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  53. 2026-08-14 01:16 UTCEG score recompute
  54. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-08-12 16:07 UTCEG score recompute
  56. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  57. 2026-08-11 15:42 UTCEG score recompute
  58. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  59. 2026-08-11 03:31 UTCEG score recompute
  60. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  61. 2026-08-09 14:58 UTCEG score recompute
  62. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  63. 2026-08-08 18:40 UTCEG score recompute
  64. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  65. 2026-08-07 18:18 UTCEG score recompute
  66. 2026-08-06 17:55 UTCEG score recompute▲ 0.90
  67. 2026-08-06 17:55 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  68. 2026-08-06 16:45 UTCEG score recompute
  69. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  70. 2026-08-06 05:15 UTCEG score recompute
  71. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  72. 2026-08-04 17:18 UTCEG score recompute
  73. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  74. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  75. 2026-08-03 18:18 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10672?
CVE-2026-10672 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. subsys/net/lib/lwm2m/lwm2mpullcontext.c copied the firmware-update Package URI into a fixed static buffer (context.uri, size CONFIGLWM2MSWMGMTPACKAGEURILEN, default 128) with memcpy(context.uri, uri, LWM2MPACKAGEURILEN), copying exactly the destination size with no length validation. The…
When was the CVE record for CVE-2026-10672 published?
The CVE record for CVE-2026-10672 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 6, 2026; the record at its source may have been updated since.
Is CVE-2026-10672 actively exploited?
CVE-2026-10672 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10672?
CVE-2026-10672 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-10672?
A fix for CVE-2026-10672 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10672

Explore →

Is Your Infrastructure Affected by CVE-2026-10672?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs