CVE-2026-10657

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. 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
Trending — 4 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
15.4%
KEV
Not listed

Published

July 5, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Out-of-bounds read in Zephyr DNS resolver mDNS suffix check (memcmp past string NUL) · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-76jh-3j5f-9vq4
github_commit

commit 448a21da12c9 (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 448a21da12c9 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/448a21da12c9ea28f7fd12c6894e03a987b17a27

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 24× 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.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 13:09 UTCEG score recompute
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-14 19:21 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  5. 2026-07-14 19:00 UTCMITRE cvelistV5CVSS v3 → 3.7 · severity → LOW
  6. 2026-07-14 14:02 UTCEG score recompute
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 14:56 UTCEG score recompute
  9. 2026-07-13 06:12 UTCEPSS rescore
  10. 2026-07-12 15:50 UTCEG score recompute
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 16:44 UTCEG score recompute
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-10 17:38 UTCEG score recompute
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 18:32 UTCEG score recompute
  17. 2026-07-08 19:23 UTCEG score recompute 1.60
  18. 2026-07-08 15:15 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-08 15:13 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-05 22:40 UTCEG score recompute
  24. 2026-07-05 22:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-10657?
CVE-2026-10657 is a medium vulnerability published on July 5, 2026. Zephyr's DNS resolver detects mDNS (.local) queries in dnsresolvename_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…
When was CVE-2026-10657 disclosed?
CVE-2026-10657 was first published in the National Vulnerability Database on July 5, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10657 actively exploited?
CVE-2026-10657 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10657?
CVE-2026-10657 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-10657?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10657, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10657

Explore →

Is Your Infrastructure Affected by CVE-2026-10657?

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