CVE-2026-7656 is a validation bypass in the IPv6 Neighbor Discovery code of the Zephyr RTOS: an operator-precedence error skipped the Hop Limit and link-local source checks, so a device with IPv6 enabled accepted spoofed Router Advertisements and neighbor messages that can redirect its traffic. NVD scores it 6.8. Zephyr fixed it for v4.5.0 with backports to v4.4, v4.3 and v3.7.
Vulnerability summary
CVSS base score
6.8
Medium severity
EPSS score (FIRST)
0.3%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-7656 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Zephyr RTOS (IPv6 Neighbor Discovery, subsys/net/ip/ipv6_nbr.c) | cpe:2.3:o:zephyrproject:zephyr:*:*:*:*:*:*:*:* | releases through v4.4.0 (GHSA-cpjw-rvwx-ph9f); NVD CPE up to and including 4.4.1; fix in v4.5.0, v4.4.1, v4.3.1 and the v3.7 branch |
What does this mean for affected devices?
Zephyr's security advisory GHSA-cpjw-rvwx-ph9f, published 2026-06-29 and rated high, describes an operator-precedence error in the IPv6 Neighbor Discovery input handlers in subsys/net/ip/ipv6_nbr.c. The Router Advertisement, Neighbor Solicitation and Neighbor Advertisement checks had the form "(A || B || C) && D", where D is icmp_hdr->code != 0. Every valid ND message carries ICMPv6 code 0, so the whole drop condition was false and the length, Hop Limit 255 and link-local source checks that RFC 4861 requires never ran. The advisory sums up the effect as "complete bypass of RFC 4861 Section 6.1.2 mandated security checks for RA and NS", and its impact list ends: "Affects all Zephyr devices with IPv6 enabled".
The CVE description on NVD explains what a forged packet can do: a forged RA "lets the attacker reconfigure the victim's default router, on-link prefixes (SLAAC), MTU" and, with CONFIG_NET_IPV6_RA_RDNSS, its DNS servers, while forged NS and NA messages poison the neighbor cache for man-in-the-middle, traffic redirection or denial of service. Because the Hop Limit check is skipped, an off-link attacker may also get packets accepted. It is a validation flaw, not a memory-safety one: the parsing primitives are bounds-safe, and the defect "has existed since the logic was introduced in 2018 and shipped in all releases through v4.4.0". NVD scores it 6.8, vector CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H; Zephyr, as CNA, scores it 8.1 with low attack complexity and lists CWE-290 (authentication bypass by spoofing) and CWE-670. NVD's CPE marks Zephyr up to and including 4.4.1 as affected.
Zephyr's Vulnerabilities page says it "has been fixed in main for v4.5.0" by PR 107902 (commit 095f064, merged 2026-04-28), with backports to v4.4 (PR 108131), v4.3 (PR 108192) and v3.7 (PR 108195), all merged by 2026-05-19. Checked against the GitHub tags on 2026-11-16, the backports are contained in the v4.4.1 and v4.3.1 release tags as well as v4.5.0, so NVD's "through 4.4.1" range is wider than the code history; on the 3.7 LTS line the fix is on the v3.7 branch and in the v3.7.3-rc1 tag, while v3.7.2 predates it.
No device vendor advisory naming affected products was found when this page was written; the exposure follows from the Zephyr version each vendor ships and whether the firmware enables IPv6. The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0033, the 26.4th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).
Device makers should check the Zephyr version and whether IPv6 is enabled in the final build, then move to v4.5.0, v4.4.1 or later, or v4.3.1 or later, or carry the v3.7 backport. Where firmware cannot be updated, RA Guard on the local switch limits who can send Router Advertisements. Our embedded TCP/IP stack vulnerabilities guide lists this CVE with Zephyr's fix channel, our Thread security guide covers the IPv6 mesh networks that Zephyr's OpenThread integration joins, and the DNS name-parser overflow in the same stack is CVE-2026-1678.
Evidence
- (A || B || C) && (code != 0) in RA/NS/NA handlers of ipv6_nbr.c; hop_limit 255 and link-local source checks bypassed; affects all Zephyr devices with IPv6 enabled; CNA CVSS 8.1 (AV:A/AC:L); CWE-290, CWE-670; published 2026-06-29; patches main #107902, v4.4 #108131, v4.3 #108192, v3.7 #108195. — Zephyr GHSA-cpjw-rvwx-ph9f
- NVD CVSS v3.1 6.8 (AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H); CPE Zephyr up to and including 4.4.1; description: forged RA reconfigures router, prefixes, MTU, DNS (RDNSS); shipped in all releases through v4.4.0. — NVD
- Fixed in main for v4.5.0 (PR 107902); fixes for v4.4 (PR 108131), v4.3 (PR 108192), v3.7 (PR 108195). — Zephyr Project documentation: Vulnerabilities
- Commit 095f064 'net: ipv6: Fix ND packets validation on input' merged to main 2026-04-28; backports merged 2026-05-01 (v4.4), 2026-05-12 (v4.3), 2026-05-19 (v3.7); backport commits contained in tags v4.4.1, v4.3.1, v4.5.0 and v3.7.3-rc1, not in v3.7.2 (GitHub compare, 2026-11-16). — Zephyr commit 095f064
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.0033 (26.4th percentile), dataset 2026-11-16, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which Zephyr versions fix CVE-2026-7656?
Zephyr fixed it on main for v4.5.0 and backported it to the v4.4, v4.3 and v3.7 branches. Checked against GitHub on 2026-11-16, the fix ships in the v4.4.1, v4.3.1 and v4.5.0 tags; on the 3.7 line it is in v3.7.3-rc1 and the v3.7 branch, and v3.7.2 does not include it.
What can an attacker do with CVE-2026-7656?
Send forged Router Advertisements, Neighbor Solicitations or Neighbor Advertisements that the device accepts. Per the CVE description, a forged RA can change the default router, prefixes, MTU and, with RDNSS enabled, DNS servers, and forged NS/NA can poison the neighbor cache for man-in-the-middle, redirection or denial of service.
Which devices are affected by CVE-2026-7656?
Zephyr's advisory says it "affects all Zephyr devices with IPv6 enabled" on releases through v4.4.0. No device vendor advisory naming specific products was found when this page was written, so the check is the Zephyr version and IPv6 setting in each firmware build.
Why do NVD and Zephyr score CVE-2026-7656 differently?
Both use an adjacent-network vector with high integrity and availability impact. NVD rates attack complexity high and scores 6.8; Zephyr, as CNA, rates it low and scores 8.1. This page uses NVD's score for the severity tile.
Questions about this page?