ASUS Router stack-based buffer overflow enables arbitrary code execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-19386?

CVE-2026-19386 is a vulnerability classified as Stack-based Buffer Overflow, affecting Router (affected versions: 3.0.0.6.102 series). This vulnerability is rated Critical, with a CVSS score of 9.3. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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.

Affected products and scope

  • ASUS Router: the default status is unaffected; the confirmed affected branch is 3.0.0.6.102 series.
  • The record does not identify specific router models or confirm the status of other firmware branches. Do not infer that later or parallel branches are safe.

Technical details

The flaw is in ASUS Router modules and is classified as a stack-based buffer overflow. An attacker-controlled configuration file is uploaded through the router configuration function; exceeding the expected buffer size can lead to arbitrary code execution. The recorded preconditions are an authenticated user, adjacent network access, low attack complexity, and no additional user interaction. The record does not identify the specific module, endpoint, file format, or control-flow details after the overflow.

Exploitability

  • Exploitation requires adjacent network access and an authenticated account with high privileges on the device.
  • The record states that no user interaction is required and that the upload operation has low complexity.
  • The supplied data marks public_exploit as false and known_exploited as null.
  • The returned CISA enrichment records exploitation as none and automatable as no. That is a scoped assessment at the time of enrichment, not proof that future exploitation is impossible.

Technical impact

The flaw can result in arbitrary code execution on an ASUS Router after an authenticated user uploads a configuration file larger than the expected buffer. The technical outcome could be loss of control over the router, allowing changes to device state or configuration and affecting network operations. Effects on systems behind the router are a risk to assess, not a confirmed scope for every deployment. The record does not specify process privileges, persistence mechanisms, or model-specific impact.

Business impact

Successful exploitation could allow code execution on the router and affect the device's confidentiality, integrity, and availability. Possible consequences include configuration changes, interference with routing behavior, or disruption of network service, but the record does not confirm a specific compromise scenario. Because a router commonly mediates network traffic, control of the device could increase risk to dependent systems; that is a possible consequence, not confirmed behavior for every model. The requirement for a highly privileged authenticated account limits the set of users who can attempt exploitation, but does not remove the potential severity if such an account is misused.

Remediation

  1. Inventory ASUS Router firmware and prioritize devices in the 3.0.0.6.102 series branch.
  2. Monitor and apply the fixed firmware or device-specific update guidance in the ASUS Security Advisory when ASUS provides a fix for the relevant device. The supplied record does not identify an exact fixed release.
  3. Until a fixed firmware state is confirmed, restrict administrative access and configuration-file upload privileges to trusted accounts and management networks. This is temporary exposure reduction, not a replacement for firmware updates.
  4. After updating, verify the installed firmware and review configuration-file uploads or configuration changes for abnormal activity.

Detection

  1. Inventory deployed ASUS Routers and identify devices belonging to the affected product branch recorded for this issue.
  2. Compare each device's installed firmware with ASUS affected-branch information before treating it as safe.
  3. If audit logging is available, review authenticated administrative logins and configuration-file uploads from adjacent network sources.
  4. Review unusually large configuration uploads and events occurring immediately before reboots, configuration changes, or abnormal network behavior. This is precautionary monitoring, not a vendor-published IOC.
  5. Do not treat the absence of matching log evidence as proof that a device is unaffected or was not exploited.
Sources (22)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.