Unauthenticated code execution via unbounded PTR-name copy
Published Mar 19, 2026 · Updated Mar 19, 2026
Stack buffer overflow in OpenWrt before 24.10.6 and 25.12.0-rc1 through 25.12.0 allows remote attackers to execute code via mDNS. The parse_question function passes an expanded PTR name from the 8,096-byte name_buffer to unbounded strcpy operations targeting 256-byte stack buffers. The umdns package must be installed and listening on the attacker’s multicast domain; no authentication or user interaction is required.
Summary
What happened
Stack buffer overflow in OpenWrt before 24.10.6 and 25.12.0-rc1 through 25.12.0 allows remote attackers to execute code via mDNS. The parse_question function passes an expanded PTR name from the 8,096-byte name_buffer to unbounded strcpy operations targeting 256-byte stack buffers. The umdns package must be installed and listening on the attacker’s multicast domain; no authentication or user interaction is required.
The record
- CVE
- CVE-2026-30871
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- OpenWrt
- Product
- OpenWrt
- Classifications
- CWE-121, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 24.10.6
- Affected versionversion=>= 25.12.0-rc1, < 25.12.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo