CVE-2026-1678 is an out-of-bounds write (CWE-787) in the DNS name parser of the Zephyr RTOS: a malicious DNS response can overflow a 255-byte name buffer in any Zephyr firmware that enables the DNS resolver with default assertion settings. NVD scores it 9.8. Zephyr fixed it for v4.4.0 and in v3.7.2, v4.2.2 and v4.3.1.
Vulnerability summary
CVSS base score
9.8
Critical severity
EPSS score (FIRST)
0.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-1678 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Zephyr RTOS (DNS resolver, CONFIG_DNS_RESOLVER) | cpe:2.3:o:zephyrproject:zephyr:*:*:*:*:*:*:*:* | before 3.7.2; 4.0.0 to before 4.2.2; 4.3.0 to before 4.3.1 (NVD); fixed on main for v4.4.0 (Zephyr GHSA-536f-h63g-hj42) |
What does this mean for affected devices?
Zephyr's security advisory GHSA-536f-h63g-hj42, published 2026-03-05 and rated critical, describes a memory-safety bug in dns_unpack_name() in subsys/net/lib/dns/dns_pack.c. The function "snapshots dest_size = net_buf_tailroom(buf) once and reuses it while appending labels", so as the name grows the stale bound no longer matches the space left and the final null terminator is written without a fresh check. Because the net_buf add helpers rely only on assertions and CONFIG_ASSERT defaults to off, "attacker-controlled labels in a DNS response can drive out-of-bounds writes". The advisory's proof of concept uses repeated 63-byte labels to exceed the default 255-byte name buffer while staying within the 512-byte answer size, overflowing roughly 100 to 200 bytes. It notes that turning assertions on converts the overflow into a crash but "is not a full fix".
NVD scores it 9.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; Zephyr, as CNA, scores it 9.4 with low confidentiality impact. NVD's CPE ranges mark Zephyr before 3.7.2, 4.0.0 to before 4.2.2, and 4.3.0 to before 4.3.1 as affected (NVD). Zephyr's Vulnerabilities page says it "has been fixed in main for v4.4.0" by PR 99683, merged 2025-11-21, and lists fixes for 4.3, 4.2 and 3.7. The 4.3 backport, PR 99830, was merged on 2025-12-03 for v4.3.1; the automatic 4.2 and 3.7 backports failed, and the corrected dns_unpack_name() ships in the v4.2.2 and v3.7.2 release tags, whose release notes list the fix as issue #99682.
This is a firmware-level bug rather than a single product: any device whose Zephyr application sets CONFIG_DNS_RESOLVER, which networked IoT firmware does whenever it resolves a cloud or update-server hostname, parses DNS answers with this code. No device vendor advisory naming affected products was found when this page was written; the exposure follows from the Zephyr version and build configuration each vendor ships.
The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0044, the 38.5th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).
Device makers should check the Zephyr version and whether CONFIG_DNS_RESOLVER is set in the final build configuration, move to v4.4.0 or later or to the patched 3.7, 4.2 or 4.3 release, and rebuild. A build without the resolver can carry a not-affected statement with the configuration as evidence. Our embedded TCP/IP stack vulnerabilities guide covers Zephyr's fix channel and this CVE's backports, and our memory corruption fix guide covers the live bounds checks the fix adds.
Evidence
- dns_unpack_name() caches tailroom once; stale bound; final null terminator written unchecked; OOB write with assertions off (default) when CONFIG_DNS_RESOLVER enabled; PoC 63-byte labels over 255-byte buffer; enabling asserts not a full fix; published 2026-03-05; CNA CVSS 9.4. — Zephyr GHSA-536f-h63g-hj42
- NVD CVSS v3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); CPE ranges before 3.7.2, 4.0.0 to before 4.2.2, 4.3.0 to before 4.3.1. — NVD
- Fixed in main for v4.4.0 (PR 99683); backport PRs for 4.3 (99830), 4.2 and 3.7. — Zephyr Project documentation: Vulnerabilities
- PR 99683 'net: dns: Fix potential buffer overflow when unpacking labels' merged 2025-11-21 into main. — Zephyr PR 99683
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.00436 (38.5th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which Zephyr versions fix CVE-2026-1678?
The fix is in main for v4.4.0 and was backported: NVD's ranges treat 3.7.2, 4.2.2 and 4.3.1 as fixed on their branches (per Zephyr's Vulnerabilities page and NVD).
Is every Zephyr device affected by CVE-2026-1678?
No. The advisory says builds that enable the DNS resolver (`CONFIG_DNS_RESOLVER`) with default assertion settings are vulnerable; firmware without the resolver does not run the affected parser (per Zephyr GHSA-536f-h63g-hj42).
Does enabling CONFIG_ASSERT fix CVE-2026-1678?
No. Zephyr's advisory says enabling assertions turns the overflow into a crash, a denial of service, but "is not a full fix"; the code needs live tailroom checks before each write (per Zephyr GHSA-536f-h63g-hj42).
Why do NVD and Zephyr give different scores for CVE-2026-1678?
NVD rates confidentiality impact high and scores 9.8; Zephyr as CNA rates it low and scores 9.4. Both use a network attack vector with no privileges or user interaction (per NVD and Zephyr GHSA-536f-h63g-hj42).
Questions about this page?