CVE-2026-10686

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).

• CWE-835

• https://github.com/zephyrproject-rtos/zephyr/commit/7d8f1afa7345975b58405d6fba18bb8c3f7cb12aPatch
• https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-4cg6-6jc4-2r6hExploit, Patch, Vendor Advisory

Published

Jul 31, 2026

Last Modified

Aug 7, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-10680The Classic (BR/EDR) L2CAP signaling handlers l2cap_br_conf_…7.6
• CVE-2026-10681In Zephyr's userspace dynamic-objects subsystem, thread_idx_…7
• CVE-2026-10682The userspace verifier z_vrfy_log_filter_set() for the log_f…7.8
• CVE-2026-10683In the Synopsys DesignWare I2C driver (drivers/i2c/i2c_dw.c)…4.6
• CVE-2026-10684In subsys/debug/coredump/coredump_shell.c, print_coredump_hd…3
• CVE-2026-10685The Zephyr Bluetooth GATT client CCC-write response handler …7.6
• CVE-2026-10687Rejected reason: This CVE Record has been rejected by the Ze…
• CVE-2026-10688A vulnerability was determined in ahujasid blender-mcp up to…5.5
• CVE-2026-1069GitLab has remediated an issue in GitLab CE/EE affecting all…7.5
• CVE-2026-10690A vulnerability was identified in wonderwhy-er DesktopComman…6.3
• CVE-2026-10691A security flaw has been discovered in wonderwhy-er DesktopC…4.3
• CVE-2026-10692A weakness has been identified in johnhuang316 code-index-mc…4.3