CVE-2026-10666

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (49th 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.8EG
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.7%CVSS: 9.8Exploit: 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).

parse_ipv4() in subsys/net/ip/utils.c (reached via net_ipaddr_parse() for strings of the form "a.b.c.d:port") copies the port substring into a fixed 17-byte stack buffer (char ipaddr[NET_IPV4_ADDR_LEN + 1]) using a length of str_len - end - 1, where str_len is the full, unbounded input length and end is only the (<=15-byte) offset of the ':' delimiter. Because the destination size is never consulted, a crafted address string with a long suffix after the colon (e.g. "1.2.3.4:" followed by hundreds of bytes) causes an out-of-bounds stack write whose length and contents are fully attacker-controlled (memcpy of the suffix plus a trailing NUL), enabling memory corruption and at minimum a denial of service, and potentially control-flow hijack. The parser is reached from the standard socket API (zsock_getaddrinfo / literal-address resolution), DNS server-string configuration, and the eswifi Wi-Fi co-processor DNS-response path, so an application that resolves a network-influenced address string is exposed. The bug was introduced when the parser was added (Zephyr v1.9.0) and shipped in all releases through v4.4.0. The fix removes the unbounded copy and validates the port length before copying into a small dedicated buffer. Note: the equivalent IPv6 "[addr]:port" path in parse_ipv6() retains the same unbounded copy at this commit and remains a separate, still-reachable instance of the defect.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.7%
EPSS %ILE
49th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 12, 2026

Last Modified

July 17, 2026

Advisory Details (3)

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

parse_ipv4: Stack-based buffer overflow with has_port = true · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-532c-7g7f-jhmh
GitHub commit

commit 6e119a636a57 (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 6e119a636a57 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/6e119a636a57be449ea21e73cad762ebc6f5ff7a
GitHub commit

commit 1c8d19a51f9a (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 1c8d19a51f9a — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/1c8d19a51f9a3c1be6de53854c8ad8c2720a0f48

Weakness Classification(2)

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 135 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 35 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10666?
CVE-2026-10666 is a critical-severity vulnerability; its CVE record was published on July 12, 2026. parseipv4() in subsys/net/ip/utils.c (reached via netipaddrparse() for strings of the form "a.b.c.d:port") copies the port substring into a fixed 17-byte stack buffer (char ipaddr[NETIPV4ADDRLEN + 1]) using a length of strlen - end - 1, where strlen is the full, unbounded input length and end is…
When was the CVE record for CVE-2026-10666 published?
The CVE record for CVE-2026-10666 was published on July 12, 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 July 17, 2026; the record at its source may have been updated since.
Is CVE-2026-10666 actively exploited?
CVE-2026-10666 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10666?
CVE-2026-10666 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-10666?
A fix for CVE-2026-10666 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-10666

Explore →

Is Your Infrastructure Affected by CVE-2026-10666?

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

Book a Demo →Browse All CVEs