# CVE-2026-10657 — zephyrproject zephyr

> As of 2026-07-05, CVE-2026-10657 is a LOW-severity vulnerability in zephyrproject zephyr, CVSS v3.1 3.7, EPSS 0.2% (13.2th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-10657 as of 2026-07-05; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-05

## What is CVE-2026-10657?

Zephyr's DNS resolver detects mDNS (.local) queries in dns_resolve_name_internal() (subsys/net/lib/dns/resolve.c) with memcmp(strrchr(query, '.'), ".local", 7), which always reads a fixed 7 bytes from the suffix pointer. When the resolved hostname's final label is shorter than 7 bytes (e.g. names ending in .org, .com, .net, .io, or a trailing dot), the comparison reads 1-2 bytes past the string's NUL terminator. The hostname (query) is the caller-supplied name passed through the standard getaddrinfo()/dns_get_addr_info()/dns_resolve_name() path and is influenceable by operators or remote inputs (server names from configuration, parsed URLs, or app-facing interfaces). On a tightly-sized buffer with no slack (for example a userspace getaddrinfo call where the hostname is copied with k_usermode_string_alloc_copy to exactly strlen+1 bytes), the over-read crosses the allocation boundary; if that boundary is unmapped (guard page, memory-domain boundary under MPU, or an address sanitizer) the over-read faults, causing a denial of service. The over-read bytes are never returned, so there is no information disclosure. The flaw is compiled only when CONFIG_MDNS_RESOLVER is enabled, exists since v1.10.0, and is fixed by replacing the fixed-length memcmp with a NUL-safe strcmp(ptr, ".local").

The record classifies CVE-2026-10657 under weakness class [CWE-125](https://intel.threadlinqs.com/cwe/CWE-125). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 92 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 3.7 — LOW (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 13.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 2.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-05

## Is CVE-2026-10657 being exploited?

It currently carries a trending score of 33 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [zephyrproject](https://intel.threadlinqs.com/vendors/zephyrproject): zephyr

## How to fix CVE-2026-10657

No vendor patch reference has been recorded for CVE-2026-10657 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-10657

No threat campaign in the Threadlinqs corpus currently references CVE-2026-10657, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on 2026-07-06.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/zephyrproject-rtos/zephyr/commit/448a21da12c9ea28f7fd12c6894e03a987b17a27)

**Other references**

- [github.com](https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-76jh-3j5f-9vq4)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-10657
Full detection coverage and IOCs for threats exploiting CVE-2026-10657 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp