Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network position
-
DeliveryAuthenticate with admin credentials
-
ExploitUpload crafted oversized config file
-
ExecutionOverflow stack buffer in router module
-
PersistExecute arbitrary code on device
-
ImpactFull router 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 three concrete prerequisites drawn from the description and CVSS vector: (1) the attacker must already possess high-privilege/administrative access to the router (PR:H) - this is an authenticated flaw, not pre-auth; (2) the attacker must be network-adjacent (AV:A), i.e. on the same local/Wi-Fi segment rather than reaching the device across the open Internet; and (3) the attacker must be able to submit a crafted configuration file through the router's upload mechanism whose size exceeds the expected buffer. The limiting factors are therefore the admin-credential requirement and the adjacent-network constraint, which together exclude anonymous Internet-wide attack; no end-user interaction is required (UI:N) once those conditions are met. |
| Impact | The CVSS 4.0 base score of 9.3 (Critical) is driven largely by the uniform High impact metrics (VC:H/VI:H/VA:H and subsequent-system SC:H/SI:H/SA:H) combined with low attack complexity, but two metrics meaningfully constrain real-world risk: AV:A means the attacker must be network-adjacent (same LAN/Wi-Fi segment, not routable Internet access) and PR:H means the attacker must already hold high-privilege (administrative) credentials on the router. This is therefore a post-authentication, adjacent-access code-execution flaw rather than a drive-by remote takeover, which tempers the headline score. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; exploitation would require chaining with credential theft or an authentication bypass to be impactful against a hardened device. Net assessment: a genuinely serious vulnerability where exploitable (full device compromise), but the PR:H + AV:A prerequisites make it a lower immediate priority than a comparably-scored unauthenticated remote flaw - patch promptly but it is not a wormable emergency on its own. |
| Exploit ScenarioDerived | An attacker who has gained administrative access to an ASUS router and sits on an adjacent network segment uploads a maliciously crafted configuration file whose contents exceed the expected buffer size, triggering a stack-based buffer overflow (CWE-121) in the router's handling module. By controlling the overflow contents the attacker overwrites the stack and executes arbitrary code on the device, taking full control of the router. No public proof-of-concept was provided in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
A stack-based buffer overflow in ASUS router firmware modules lets an attacker who already holds administrative credentials on the device and is connected to the same local or Wi-Fi network segment execute arbitrary code by uploading a crafted configuration file that exceeds an expected buffer size. The flaw is rated CVSS 4.0 9.3 (Critical) and assessed as CVSS 3.1 AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, because successful exploitation yields full compromise of confidentiality, integrity and availability of the router, although the adjacent-network (AV:A) and high-privilege (PR:H) requirements exclude anonymous Internet-wide attack. No public exploit code has been identified at time of analysis, the issue is not listed in CISA KEV, and no EPSS score was supplied; vendor guidance is available through the ASUS Security Advisory.
RemediationAI
Apply the firmware update described in the 'Security Update for ASUS Router Firmware' section of the ASUS Security Advisory at https://www.asus.com/security-advisory; the exact fixed version number is not specified in the available data, so verify the current release for your router model on ASUS's support site before and after updating. Until the device is patched, the most effective compensating control is to eliminate the two prerequisites: restrict administrative access so that only trusted wired management hosts can reach the router's web UI (disable WAN/remote administration and, where supported, limit admin access to a specific LAN interface), and rotate the administrative password, since the flaw requires high-privilege credentials - the trade-off is reduced convenience for remote management. Additional hardening includes disabling or removing unneeded services that expose the configuration upload path (for example AiCloud, USB/network file sharing and remote configuration restore), isolating guest and IoT devices on separate SSIDs/VLANs so an adjacent attacker on the same wireless segment cannot reach the admin interface, and monitoring logs for unexpected configuration uploads or firmware/host reboots. These measures reduce exposure but do not eliminate the underlying overflow, so firmware upgrade remains the only complete fix.
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 vulnerability is a classic stack-based buffer overflow (CWE-121) in the configuration-file handling path of ASUS router firmware: when a configuration file is uploaded, the parsing routine copies attacker-controlled data into a fixed-size stack buffer without validating length, so an oversized file overflows adjacent stack memory and can redirect execution to attacker-supplied code. The CPE entry cpe:2.3:a:asus:router:*:*:*:*:*:*:*:* uses a wildcard version, indicating the advisory covers multiple ASUS router models and firmware branches rather than one SKU, so administrators must map their specific model to the corresponding firmware release. Attack surface is the device's administrative configuration import/restore feature rather than a WAN-facing service, which is consistent with the assessed vector requiring network adjacency (AV:A) and high privileges (PR:H) but no user interaction (UI:N). ASUS's own CVSS 4.0 score of 9.3 reflects uniform High impact across vulnerable and subsequent systems (VC:H/VI:H/VA:H, SC:H/SI:H/SA:H) with low attack complexity; the assessed CVSS 3.1 equivalent keeps the same impact (S:U, C:H/I:H/A:H) while making the adjacency and privilege constraints explicit. Root cause remediation therefore lies in bounds checking and hardened input validation in the firmware's configuration parser.
Know when Router 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:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Adjacent vector (AV:A) and administrative upload capability set PR:H; crafted file reliably triggers the overflow (AC:L) yielding full code execution, so C/I/A:H; scope unchanged as code runs on the router itself.
Primary rating from Vendor (ASUS).
CVSS VectorVendor: ASUS
DescriptionCVE.org
A stack-based buffer overflow in the ASUS router modules allows an authenticated nearby user to execute arbitrary code via a crafted configuration file upload that exceeds the expected buffer size.Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.
Executive ViewAI
ASUS router firmware shipped across the vendor's consumer and small-business device lines contains a critical stack-based buffer overflow that can hand an attacker complete control of the device - and therefore of the network traffic, VPN tunnels and connected endpoints behind it. Exploitation is constrained: the attacker must already hold administrative credentials on the router and be positioned on the same local or Wi-Fi segment, so the exposure is concentrated in insider, compromised-credential and adjacent-network scenarios rather than opportunistic internet-wide scanning. Leadership should care because a fully compromised router is a silent, persistent vantage point for interception and lateral movement into the wider corporate network, and no vendor patch is available today.
No vendor-released patch identified at time of analysis; apply vendor patch when available. In the interim: rotate all administrative credentials to strong unique values and remove default accounts; disable remote/WAN administration, cloud management and any internet-exposed management services; restrict the administrative interface to a dedicated management VLAN or explicit trusted-host allowlist, since the flaw requires an adjacent-network position; segment guest, IoT and user Wi-Fi networks away from the router's management plane; limit configuration-file import rights to a small set of named administrators; log and alert on configuration upload and admin login events, and monitor for unexpected configuration changes or outbound traffic from the router; isolate or replace devices that cannot be adequately segmented.
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.
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Related Vulnerabilities in ASUS Router Code Execution and Info Disclosure
View all 4Unauthenticated remote attackers can enable Telnet on TOTOLINK X5000R AX1800 routers running firmware V9.1.0u.6369_B2023
Depending on the configuration of the route permission table in file 'saprouttab', it is possible for an unauthenticated
OS command injection in Netcore NAP930 firmware 0.1.241010.141410 allows unauthenticated remote attackers to execute arb
An unauthenticated OS command injection in the CGI handler of Netcore NR289-GE firmware 1.4.5102 lets remote attackers e
Missing authorization in Netcore NBR100V2 firmware 1.3.240614.030928 allows remote unauthenticated attackers to modify d
Authenticated administrators of ASUS routers can execute arbitrary commands on the device by uploading a crafted file th
Unauthenticated network attackers can bypass authentication in the Netcore NR289-GE router's boa_temp web handler and ab
Remote unauthenticated OS command injection in Netcore NR289-GE firmware 1.4.5102 allows attackers to execute arbitrary
Unauthenticated OS command injection in the Netcore NR289-GE router (firmware 1.4.5102) lets any remote attacker who can
A stack-based buffer overflow in the devdiscover service of FAST FAC1900R firmware 20190827_2.0.2 lets unauthenticated r
Unauthenticated OS command injection in the Netcore NBR200V2 router's Web Management Interface (firmware 1.3.241127.0712
Authenticated administrators of certain ASUS router models can abuse leftover debug code in the device's web management
EUVD-2026-94157
GHSA-rx2g-2998-5867
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB