Skip to content
COOEY

EXPOSURES › CVE-2026-30871

CVE-2026-30871

CRITICAL
DETAIL
SourceNVD · cve Published2026-03-19 CVSS9.8 Referencehttps://nvd.nist.gov/vuln/detail/CVE-2026-30871 ↗
⚡ RCE SHAME 72/100 unpatchedexploited-in-wildrce

OpenWrt embedded devices running versions prior to 24.10.6 and 25.12.1 are vulnerable to a stack-based buffer overflow in the mdns daemon that allows remote code execution via crafted DNS packets.

A stack-based buffer overflow in the mdns daemon of OpenWrt allows remote code execution when processing PTR queries for reverse DNS domains. This vulnerability is triggered by normal multicast DNS packet processing and has been fixed in later versions. DIB organizations must ensure all embedded network devices are patched to versions 24.10.6 or 25.12.1 to prevent potential compromise of network infrastructure.

Shame score — The vulnerability allows remote code execution through normal network traffic without authentication, posing a significant risk to embedded devices used in defense networks.

▸ RECOMMENDED ACTION  Remote code execution — patch the affected products on priority.

DESCRIPTION

OpenWrt Project is a Linux operating system targeting embedded devices. In versions prior to 24.10.6 and 25.12.1, the mdns daemon has a Stack-based Buffer Overflow vulnerability in the parse_question function. The issue is triggered by PTR queries for reverse DNS domains (.in-addr.arpa and .ip6.arpa). DNS packets received on UDP port 5353 are expanded by dn_expand into an 8096-byte global buffer (name_buffer), which is then copied via an unbounded strcpy into a fixed 256-byte stack buffer when handling TYPE_PTR queries. The overflow is possible because dn_expand converts non-printable ASCII bytes (e.g., 0x01) into multi-character octal representations (e.g., \001), significantly inflating the expanded name beyond the stack buffer's capacity. A crafted DNS packet can exploit this expansion behavior to overflow the stack buffer, making the vulnerability reachable through normal multicast DNS packet processing. This issue has been fixed in versions 24.10.6 and 25.12.1.

AFFECTED FEDRAMP PRODUCTS · 0
No correlated FedRAMP products.