Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain admin access on adjacent network
-
ExploitSend HTTP request with oversized input
-
ExecutionOverflow fixed-size stack buffer
-
ImpactCrash router and deny service
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 the attacker to be positioned on the adjacent/local network segment (AV:A - e.g., connected to the router's LAN or Wi-Fi, not reachable from the internet) AND to already possess high-privilege administrative authentication to the router's web interface (PR:H). With those preconditions met, the attacker sends an HTTP request to the management interface containing an input field longer than the expected length, triggering the stack buffer overflow. Limiting factors that reduce realistic risk: no remote/internet exploitation, no unauthenticated access, and the required admin privilege level is the same level needed to reboot or reconfigure the device anyway; impact is confined to denial of service / operational corruption (no confidentiality loss). Specific affected models and firmware versions are not enumerated in the provided advisory reference. |
| Impact | The input CVSS 4.0 base score of 8.2 (High) is driven by high integrity and availability impact (VI:H/VA:H/SA:H), but two metrics meaningfully constrain real-world risk: AV:A means the attacker must be on the adjacent/local network (LAN or Wi-Fi, not the public internet), and PR:H means the attacker must already hold high-privilege (administrative) access to the router. An admin-authenticated adjacent attacker is a high bar, and such an actor can typically already reboot or reconfigure the device, which blunts the practical value of a DoS primitive. There is no confidentiality impact (VC:N), and the outcome is corruption/denial of service rather than code execution or data theft per the description. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no signal of active or probable exploitation - this reads as a high-CVSS-but-moderate-real-priority issue rather than an urgent threat. Note a tension: the CWE-121 (stack buffer overflow) and tags suggest a memory-corruption primitive that could theoretically exceed DoS, but the vendor description explicitly scopes impact to corruption of device operations and denial of service only; treat RCE potential as unconfirmed. |
| Exploit ScenarioDerived | An attacker who has already obtained administrative credentials to an affected ASUS router and who sits on the same local/adjacent network sends a crafted HTTP request to the router's web management interface with a field exceeding the expected length. This overflows a fixed-size stack buffer (CWE-121), corrupting device operations and crashing the service, resulting in denial of service. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 20, 2026
A stack-based buffer overflow in the web management interface of certain ASUS router models allows an attacker positioned on the adjacent network segment (LAN or Wi-Fi) who already holds high-privilege administrative credentials to corrupt device operations and cause a denial of service by sending an HTTP request containing an input field longer than the expected length. The 8.2 CVSS 4.0 score reflects high integrity and availability impact, but confidentiality is unaffected and the preconditions are substantial: no internet-facing exposure and no unauthenticated path, since the required admin session is already sufficient to reboot or reconfigure the device. No public exploit code or confirmed active exploitation was identified at time of analysis, and the advisory does not enumerate the specific affected models or firmware builds.
RemediationAI
Patch status: patch available per vendor advisory - ASUS publishes fixed firmware in the 'Security Update for ASUS Router Firmware' section of its Security Advisory (https://www.asus.com/security-advisory); exact patched version numbers are not enumerated in the provided data, so verify your model's build against that page and update via the router's firmware upgrade interface or ASUS support download. Until updated, reduce exposure with specific controls: disable WAN/remote web administration and any cloud or "ASUSWRT" remote access features so the management interface is reachable only from trusted LAN segments (side effect: remote management workflows must move behind a VPN); restrict administrative access to a dedicated management VLAN or wired segment and avoid administering the router over untrusted Wi-Fi or guest networks; enforce unique, strong admin credentials and remove unused accounts to raise the PR:H bar (side effect: none beyond operational discipline - note this does not fix the flaw, since a legitimate admin session is already sufficient to trigger it); and monitor for repeated malformed or oversized HTTP requests to the router's management port followed by daemon restarts or reboots, which may indicate attempted triggering. Because the underlying copy routine is unfixed without the vendor firmware, network segmentation and removal of the admin interface from reachable segments are the only effective compensating controls.
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 CWE-121, a stack-based buffer overflow in which the firmware copies HTTP request input into a fixed-size stack buffer without validating the length against the destination capacity. Because the management interface is a web service reachable from the router's LAN and Wi-Fi segments, a crafted request with an overlong field writes past the buffer boundary, smashing adjacent stack memory (saved registers, return addresses) and destabilizing the HTTP daemon or the device itself. The reported tags - buffer overflow, stack overflow, denial of service - align with this class; note that the description's phrasing ("buffer copy without checking size of input") corresponds to CWE-120 while the assigned CWE is CWE-121, a distinction that matters for exploitability since stack corruption can in principle permit control-flow influence, though the assessed impact here is limited to integrity and availability with no confidentiality loss. The provided data contains no CPE strings, so the exact model and firmware matrix cannot be confirmed beyond "certain ASUS router models"; the ASUS Security Advisory is the authoritative source for the affected list.
Know when Asus 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:N/VI:H/VA:H/SC:N/SI:N/SA:H
Adjacent vector (AV:A) and administrative privilege (PR:H) per the description; low complexity; no confidentiality impact but high integrity/availability impact from memory corruption and DoS.
Primary rating from Vendor (54bf65a7-a193-42d2-b1ba-8e150d3c35e1).
CVSS VectorVendor: 54bf65a7-a193-42d2-b1ba-8e150d3c35e1
DescriptionCVE.org
Buffer Copy without Checking Size of Input in certain ASUS router models allows an adjacent authenticated user to corrupt device operations and cause a denial of service via an HTTP request with input exceeding the expected length. Refer to the ' Security Update for ASUS Router Firmware' section on the ASUS Security Advisory for more information.
Executive ViewAI
A high-severity memory-corruption flaw (CVE-2026-17518) in the web management interface of certain ASUS router models can be triggered by an oversized input field to crash or destabilize the device, interrupting network connectivity at any site that depends on the affected hardware. The practical risk is bounded: the attacker must already be on the local network segment and already hold administrative credentials on the device, and no public exploit code or confirmed active exploitation was identified at time of analysis. Leadership should care because no vendor patch is available yet, the advisory does not name the affected models or firmware builds, and branch, retail, or remote-site connectivity could be disrupted until firmware is released and deployed.
No vendor-released patch identified at time of analysis. Interim mitigations: disable WAN-facing and remote web management on all ASUS routers; restrict the administrative interface to a dedicated management VLAN or explicit host allowlist; segment guest, IoT, and wireless client networks from management planes; enforce unique strong credentials and minimal admin accounts with session timeouts; alert on abnormally long HTTP parameters sent to router admin endpoints; prefer CLI/SSH administration where supported and disable the web UI when it is not operationally required; and maintain an inventory of affected models so firmware can be applied immediately on release.
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.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Related Vulnerabilities in ASUS Router Buffer Overflow and Missing Auth
View all 2common.c in infosvr in ASUS WRT firmware 3.0.0.4.376_1071, 3.0.0.376.2524-g0013f52, and other versions, as used in RT-AC
Buffer overflow in the CxDbgPrint function in the ipswcom.dll ActiveX component 1.0.0.1 for ASUS Net4Switch 1.0.0020 all
Buffer overflows in networkmap on ASUS RT-N56U, RT-N66U, RT-AC66U, RT-N66R, RT-AC66R, RT-AC68U, RT-AC68R, RT-N66W, RT-AC
The Network Analysis tab (Main_Analysis_Content.asp) in the ASUS RT-AC68U and other RT series routers with firmware befo
Multiple buffer overflows in web.c in httpd on the ASUS RT-N56U and RT-AC66U routers with firmware 3.0.0.4.374_979 allow
Compromised builds of the ASUS Live Update client, distributed through ASUS's own trusted update channel, could cause de
Session hijack vulnerability in httpd on ASUS RT-N56U, RT-N66U, RT-AC66U, RT-N66R, RT-AC66R, RT-AC68U, RT-AC68R, RT-N66W
An issue was discovered in AsusWRT before 3.0.0.4.384_10007. Rated critical severity (CVSS 9.8), this vulnerability is r
An issue was discovered in AsusWRT before 3.0.0.4.384_10007. Rated critical severity (CVSS 9.8), this vulnerability is r
Buffer overflow in Broadcom ACSD allows remote attackers to execute arbitrary code via a long string to TCP port 5916. R
Asus RT-AC68U <3.0.0.4.385.20633 and RT-AC5300 <3.0.0.4.384.82072 are affected by a buffer overflow in blocking_request.
ASUS ASMB8 iKVM firmware through 1.14.51 allows remote attackers to execute arbitrary code by using SNMP to create exten
EUVD-2026-104783
GHSA-8j23-4jj7-m65q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB