CVE-2026-10686

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed 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).

Zephyr's IPv6 forwarding path re-sent routed unicast packets without ever decrementing the IPv6 hop limit. Both routing branches of ipv6_route_packet() (subsys/net/ip) were affected: the explicit-route path (net_route_packet()) and the on-link cross-interface path (net_route_packet_if()). Each set the packet forwarding flag and called net_send_data() with the hop limit untouched and no expiry check.

Per RFC 8200 the hop-limit decrement is the mechanism that bounds packet lifetime and terminates routing loops; without it, a device acting as an IPv6 router relays looping packets indefinitely. An on-path attacker who can induce or exploit a transient L3 loop turns it into a permanent forwarding storm, causing CPU/bandwidth resource exhaustion (availability DoS) on the forwarder and adjacent links; path-discovery and loop diagnostics that rely on hop-limit expiry are also defeated.

Affected configurations. In every affected release the forwarding path is reached via CONFIG_NET_ROUTE (enabled by default when CONFIG_NET_IPV6_NBR_CACHE is set), together with CONFIG_NET_ROUTING for cross-interface routing. Note that CONFIG_NET_IPV6_FORWARDING and CONFIG_NET_IPV4_FORWARDING — which appear in the fix and in this advisory's evidence notes — were introduced after v4.4.0, when the routing options were split and renamed; they do not exist in any affected release. When auditing a v4.4.1-or-earlier configuration, look for CONFIG_NET_ROUTE and CONFIG_NET_ROUTING.

IPv4 is not affected in any release. The IPv4 forwarding path (net_route_ipv4_packet() in route_ipv4.c) was added after v4.4.0 and has never shipped in a release. Its TTL decrement and IPv4 header-checksum recomputation landed on main as part of the same fix, so the evidence notes below discuss it, but no released version is reachable by way of IPv4.

Affected releases are v1.8.0 through v4.4.1: v1.8.0 introduced net_route_packet() and v2.2.0 added net_route_packet_if(), and neither decremented the hop limit. v4.3.1 carries the explicit-route fix but not the on-link one, so it is affected as well. Fixed on main by 7d8f1afa7345 (explicit-route path) and 589eadc74efa (on-link path).

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
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.5%
EPSS %ILE
42nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or 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 none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 31, 2026

Last Modified

August 7, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
githubMentions a patch (unverified)

Missing hop-limit decrement on IPv6 forwarding path allows unbounded packet looping (DoS) in Zephyr routers · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-4cg6-6jc4-2r6h
github_commit

commit 7d8f1afa7345 (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 7d8f1afa7345 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/7d8f1afa7345975b58405d6fba18bb8c3f7cb12a

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 115 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10686?
CVE-2026-10686 is a high vulnerability published on July 31, 2026. Zephyr's IPv6 forwarding path re-sent routed unicast packets without ever decrementing the IPv6 hop limit. Both routing branches of ipv6routepacket() (subsys/net/ip) were affected: the explicit-route path (netroutepacket()) and the on-link cross-interface path (netroutepacketif()). Each set the…
When was CVE-2026-10686 disclosed?
CVE-2026-10686 was first published on July 31, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10686 actively exploited?
CVE-2026-10686 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10686?
CVE-2026-10686 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-10686?
A fix for CVE-2026-10686 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-10686

Explore →

Is Your Infrastructure Affected by CVE-2026-10686?

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

Book a Demo →Browse All CVEs