Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network position (LAN/Wi-Fi)
-
DeliverySend crafted device name to router
-
ExploitOverflow stack buffer in firmware
-
ExecutionExecute arbitrary commands as root
-
ImpactFull device compromise
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network adjacency (AV:A): the attacker must be on the same local/L2 network segment or within wireless range of the router, not reaching it over the internet - this proximity requirement is the primary limiting factor. The flaw is triggered via a crafted device name against affected ASUS router firmware, and the advisory references the AiCloud feature, so the vulnerable code path is plausibly tied to that feature set - though the input does not confirm whether AiCloud must be explicitly enabled, so that conditionality is unverified. Within reach, no authentication (PR:N), no user interaction (UI:N), and low complexity (AC:L) are needed. Exact vulnerable firmware versions/models are not enumerated in the available data. |
| Impact | This is a genuine high-priority flaw, though several real-world constraints temper the raw score. The input 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 yielding full high impact to confidentiality, integrity and availability (VC:H/VI:H/VA:H) - consistent with the description's claim of arbitrary command execution as root. The decisive limiter is AV:A (adjacent, not network): the attacker must be 'nearby' - on the same local/L2 segment or within wireless range - not on the open internet, which sharply narrows the realistic attacker population versus a comparable AV:N router bug. On the decision signals: the vuln.today priority label is 'this_week' (not act_now/emergency). No EPSS score, no CISA KEV listing, and no SSVC automatable/exploitation fields were supplied, so exploitation probability cannot be quantified from the input. No proof-of-concept or exploit reference is present either - only a generic ASUS advisory link. So the signals are moderately consistent: serious technical impact and trivial complexity, but gated by physical/network proximity and with no evidence yet of active exploitation or public exploit code. Treat it as a prompt-patch item for exposed/multi-tenant networks rather than an internet-wide emergency; the 'this_week' label aligns with that reading. |
| Exploit ScenarioDerived | An attacker within the router's local or wireless network range (for example on a shared/guest Wi-Fi or an untrusted LAN segment) sends a crafted device name to a vulnerable ASUS router running the affected firmware, overflowing a stack buffer and executing arbitrary commands as root without any credentials or user interaction. Given AV:A and AC:L, the attack is low-complexity but requires network adjacency, not internet reachability. No public exploit code is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 04, 2026
Unauthenticated attackers who sit on the same local/L2 network segment or within wireless range of an affected ASUS router can trigger a stack-based buffer overflow using a crafted device name and execute arbitrary commands with root privileges. ASUS scores the issue 8.7 (CVSS 4.0 AV:A/AC:L/PR:N/UI:N/VC:H/VI:H/VA:H), and our independent assessment maps to CVSS 3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; the network-adjacency requirement is the main real-world limiting factor, and the specific vulnerable models and firmware builds are not enumerated in the available data. No public exploit code or CISA KEV entry was identified at time of analysis, and the vendor-referenced mitigation is the AiCloud security update described in the ASUS advisory.
RemediationAI
Apply the firmware security update described in the "Security Update for ASUS Router AiCloud Feature" section of the ASUS security advisory at https://www.asus.com/security-advisory; the available data does not enumerate the exact fixed firmware version or the affected model list, so the version to install must be read from that advisory per model rather than inferred here. Where an immediate update is not possible, the exposure is bounded by the attacker's need for network adjacency, so isolating the router's management and wireless client surface from untrusted L2 segments and restricting who can associate with or sit adjacent to the device reduces reachability, at the cost of tighter network segmentation and guest/IoT isolation. Because ASUS's advisory frames the fix around AiCloud, disabling or restricting the AiCloud feature is a plausible additional reduction in exposure for routers that do not need it, but the supplied sources do not confirm that AiCloud must be enabled for exploitation, so this should be treated as defense in depth rather than a verified workaround, and it removes cloud-based remote-access functionality for legitimate users.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is a stack-based buffer overflow (CWE-121), meaning a fixed-size buffer allocated on the stack is overrun by data that exceeds its bounds; per the advisory, the overflowing input is a crafted device name. The advisory's remediation section is titled "Security Update for ASUS Router AiCloud Feature", which plausibly ties the vulnerable code path to AiCloud-related device-name handling, although the supplied sources do not confirm whether AiCloud must be explicitly enabled for the overflow to be reachable, and they do not describe the specific parsing routine or copy operation that overruns the buffer. Because the corrupted memory is stack-resident, successful exploitation can redirect control flow and, given the firmware's privilege model, lead to command execution as root; the CVSS 4.0 vector's PR:N and UI:N values indicate the attacker needs neither credentials nor user interaction, while AV:A reflects that the attacker must already be positioned on the adjacent network segment or within wireless range. The CPE entry (cpe:2.3:a:asus:router_firmware:*:*:*:*:*:*:*:*) uses a wildcard version field, so the affected firmware range is effectively open-ended in the available data rather than pinned to specific releases.
Know when Router Firmware gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Nearby/adjacent attacker gives AV:A; no credentials or interaction means PR:N/UI:N; root-level command execution yields full C:H/I:H/A:H with no scope change.
Primary rating from Vendor (ASUS).
CVSS VectorVendor: ASUS
DescriptionCVE.org
Stack-based buffer overflow in certain ASUS Router firmware allows an unauthenticated nearby attacker to execute arbitrary commands with root privileges via a crafted device name. Refer to the ' Security Update for ASUS Router AiCloud Feature ' section on the ASUS Security Advisory for more information.
Executive ViewAI
A high-severity vulnerability in certain ASUS routers allows unauthenticated attackers on the same local network or within wireless range to execute arbitrary commands with root privileges. This could enable full compromise of the router, affecting all users and devices on the network. Leadership should prioritize immediate mitigation due to the potential for data breaches and service disruption.
Apply vendor-recommended AiCloud security update; segment network to limit exposure; disable AiCloud if not needed; monitor for anomalous activity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
More in Router Firmware
View allMikroTik v6.40.5 devices allow remote attackers to cause a denial of service via a flood of ICMP packets. Rated high sev
A vulnerability in MikroTik Version 6.41.4 could allow an unauthenticated remote attacker to exhaust all available CPU a
Authentication Bypass by Primary Weakness vulnerability in DTS Electronics Redline Router firmware allows Authentication
Authentication Bypass by Alternate Name vulnerability in DTS Electronics Redline Router firmware allows Authentication B
BEC Technologies Multiple Routers sys ping Command Injection Remote Code Execution Vulnerability. Rated high severity (C
Out-of-bounds write in certain ASUS router firmware lets an unauthenticated attacker on the same adjacent network send a
BEC Technologies Multiple Routers Cleartext Password Storage Information Disclosure Vulnerability. Rated medium severity
BEC Technologies Multiple Routers Insufficiently Protected Credentials Information Disclosure Vulnerability. Rated mediu
BEC Technologies Multiple Routers Authentication Bypass Vulnerability. Rated medium severity (CVSS 5.3), this vulnerabil
EUVD-2026-116688
NVD
CVE.org
GitHub PoC
Exploit-DB