dbcve.org
Rt Ac51u FirmwareOperating system · Asus

CVE-2018-8826

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ASUS RT-AC51U, RT-AC58U, RT-AC66U, RT-AC1750, RT-ACRH13, and RT-N12 D1 routers with firmware before 3.0.0.4.380.8228; RT-AC52U B1, RT-AC1200 and RT-N600 routers with firmware before 3.0.0.4.380.10446; RT-AC55U and RT-AC55UHP routers with firmware before 3.0.0.4.382.50276; RT-AC86U and RT-AC2900 routers with firmware before 3.0.0.4.384.20648; and possibly other RT-series routers allow remote attackers to execute arbitrary code via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Multiple ASUS RT-series routers contain a critical remote code execution vulnerability in their firmware. Attackers can execute arbitrary code via unspecified vectors, likely through the router's web management interface or network services. The vulnerability affects both consumer and prosumer router models across multiple firmware branches.

MitigationUpdate router firmware to the specified patched versions for each model. For routers reaching end-of-life without patches, replace the device or implement strict network segmentation to limit exposure to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rt Ac51u FirmwareOperating system
Affected:= 3.0.0.4.380.8228
Rt Ac58u FirmwareOperating system
Affected:= 3.0.0.4.380.8228
Rt Ac66u FirmwareOperating system
Affected:= 3.0.0.4.380.8228
Rt Ac1750 FirmwareOperating system
Affected:= 3.0.0.4.380.8228
Rt N12 D1 FirmwareOperating system
Affected:= 3.0.0.4.380.8228
Rt Ac52u B1 FirmwareOperating system
Affected:= 3.0.0.4.380.10446
Rt Ac1200 FirmwareOperating system
Affected:= 3.0.0.4.380.10446
Rt N600 FirmwareOperating system
Affected:= 3.0.0.4.380.10446

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Log into the router web management interface (typically 192.168.1.1) and navigate to the Administration or System section to view the device model name, or check the product label on the router itself
    Affected if Router model is one of: RT-AC51U, RT-AC58U, RT-AC66U, RT-AC1750, RT-N12 D1, RT-AC52U B1, RT-AC1200, or RT-N600
  2. Check installed firmware version
    In the router web interface, go to Administration > Firmware Upgrade or System > Firmware Version to view the currently installed firmware build number
    Affected if Firmware version is exactly 3.0.0.4.380.8228 (for RT-AC51U, RT-AC58U, RT-AC66U, RT-AC1750, RT-N12 D1) or exactly 3.0.0.4.380.10446 (for RT-AC52U B1, RT-AC1200, RT-N600)
  3. Verify remote management is accessible
    Check if the router web interface is accessible from the WAN/internet side. Look for settings under Advanced > WAN > Port Forwarding or Administration > System > Remote Management. Try accessing the router IP from an external network on port 8080 or 8443
    Affected if Remote management (WLAN or WAN access) is enabled and the router is directly exposed to the internet
  4. Confirm network exposure
    Determine if the router is deployed in a location where it can be reached by untrusted networks. Check if WAN port has a public IP and firewall rules allow inbound connections to router services
    Affected if Router WAN interface has direct internet connectivity without intermediate firewall protection

You are affected if you own any of the listed ASUS RT models and your installed firmware version exactly matches 3.0.0.4.380.8228 or 3.0.0.4.380.10446 depending on model, especially if remote management is enabled or the router is internet-facing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update router firmware to the specified patched versions for each model. For routers reaching end-of-life without patches, replace the device or implement strict network segmentation to limit exposure to untrusted networks.

Recommended fix High confidence

Latest available firmware from ASUS for the specific router model (e.g., 3.0.0.4.380.8228 or later for RT-AC51U/RT-AC58U/RT-AC66U/RT-AC1750/RT-N12 D1; 3.0.0.4.380.10446 or later for RT-AC52U B1/RT-AC1200/RT-N600)

  1. 1. Identify the exact ASUS router model from the affected list (RT-AC51U, RT-AC58U, RT-AC66U, RT-AC1750, RT-ACRH13, RT-N12 D1, RT-AC52U B1, RT-AC1200, RT-N600)
  2. 2. Access the ASUS support website at www.asus.com and navigate to the product support page for your specific router model
  3. 3. Locate the firmware download section and identify the latest available firmware version
  4. 4. Download the most recent firmware version that is newer than the vulnerable versions (newer than 3.0.0.4.380.8228 or 3.0.0.4.380.10446 depending on model)
  5. 5. Access the router's web administration interface (typically at 192.168.1.1)
  6. 6. Navigate to the Administration or Firmware Upgrade section
  7. 7. Upload and apply the downloaded firmware file
  8. 8. Wait for the router to complete the upgrade process and reboot
Caveat Firmware upgrades on routers may reset configuration to defaults; backup current settings before upgrading and reconfigure after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rt Ac51u Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-8826 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-8826 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data