ASUS Router Firmware CVE-2026-84729

Exploitation requires the attacker to be on the same adjacent network as the device (AV:A - e.g., connected to the router's Wi-Fi or local LAN segment), not reachable from the general internet by default. Within that position the attack is unauthenticated (PR:N) and requires no user interaction (UI:N), achieved by sending a single crafted packet to the affected ASUS router firmware. The primary limiting factor is this adjacency requirement, which prevents mass internet-wide exploitation; additionally, only 'certain' ASUS router firmware builds are affected, so exposure depends on the specific model and firmware version in use, which the available sources do not enumerate. The available sources do not describe the exact packet or interface that triggers the out-of-bounds write.

This is a genuine but geographically-constrained risk. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N) describes an adjacent-network, low-complexity, unauthenticated attack with no user interaction, and the impact is integrity and availability high (VI:H/VA:H) with no confidentiality loss (VC:N) - consistent with a CWE-787 out-of-bounds write that corrupts memory or crashes the device. The vuln.today decision label is 'this_week', indicating elevated but not emergency urgency. Key tempering signal: the attack vector is Adjacent (AV:A), not Network - the attacker must be on the same local/adjacent segment (e.g., Wi-Fi or LAN), so this is NOT internet-wide remotely exploitable against default WAN interfaces, which materially narrows the real-world exploitation surface compared to a true AV:N router flaw. No EPSS score was provided, so exploitation probability cannot be quantified. The CVE is not in CISA KEV and no working exploit is referenced, so there is no public exploit identified at time of analysis. Net: a real priority to patch (unauthenticated, low-complexity, high impact), but the adjacency requirement and absence of exploitation evidence place it below internet-facing unauthenticated RCE in triage order.

An attacker who has gained access to the same local network as the router - for example by joining an open or compromised Wi-Fi network - sends a specially crafted packet to the device, triggering an out-of-bounds write in the vulnerable firmware. The result is either memory corruption that could be leveraged to alter device behavior or, more readily, a denial-of-service that crashes or reboots the router. No public exploit is identified at time of analysis and the exact trigger is not described in the available sources.