ASUS Router Firmware Exposes DDNS Credentials Through System Logs

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-16528?

CVE-2026-16528 is a vulnerability classified as Insertion of Sensitive Information into Log File, affecting Router (affected versions: 3.0.0.4.386 series, 3.0.0.4.388 series, and other affected versions). This vulnerability is rated High, with a CVSS score of 8.4. Current sources do not report this vulnerability as exploited.

Overview

Original source data

Insertion of Sensitive Information into Log File in certain ASUS router models allows a remote authenticated attacker to obtain DDNS credentials from the system log, potentially enabling modification of DNS settings.Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.

Affected products and scope

  • ASUS Router has default_status set to unaffected, but the following branches are explicitly recorded as affected:
  • 3.0.0.4.386 series.
  • 3.0.0.4.388 series.
  • 3.0.0.6.102 series.
  • The record does not identify the specific router models included in those branches.
  • No fixed release or precise version boundary is supplied, so other branches must not be assumed to be safe.

Technical details

This is a CWE-532 flaw in which firmware for certain ASUS Router models writes sensitive DDNS credentials to the system log. The attacker must be remote, authenticated with high privileges, and able to reach the device from an adjacent network. After obtaining the credentials from the log, the attacker may be able to use them to modify the router's DNS settings. The record does not identify the triggering request, administrative operation, log endpoint, or exact condition that causes the credentials to be written. It also does not identify the specific router models, log format, or whether other configurations mask the credentials.

Exploitability

The record describes remote exploitation from an adjacent network and requires an authenticated account with high privileges. The attack is described as low complexity and does not require user interaction. The available information does not describe an Internet-wide unauthenticated attack path, but devices reachable from a nearby network segment should still be reviewed. The record marks public exploit as false and provides no exploit details. It does not establish active exploitation.

Technical impact

The flaw exposes DDNS credentials from the system log, creating a direct confidentiality impact for authentication data. Possession of those credentials may allow an attacker to modify DNS settings, affecting the integrity of router configuration and potentially disrupting services that depend on DNS. Exploitation requires a high-privilege authenticated account and adjacent network reachability, so the record does not describe an unauthenticated attack from any network location. It does not confirm router takeover, an actual DNS change, or impact to downstream systems.

Business impact

  • DDNS credentials may be disclosed to an attacker who has the required authenticated access to the system log.
  • Use of exposed credentials may allow modification of the router's DNS settings.
  • DNS changes could affect name resolution and services that depend on those names, although the record does not confirm a specific DNS change or incident.
  • The record provides no evidence that the impact extends to other devices or systems.

Remediation

  1. Check the ASUS Security Advisory and apply the firmware update for the exact router model and affected branch when ASUS provides the corresponding fix.
  2. Prioritize identification of devices running the affected branches and restrict administrative, log, and DDNS access to necessary accounts from adjacent networks.
  3. If DDNS credentials may have appeared in logs or been accessed by an unauthorized party, rotate the credentials and verify the router's DNS settings.
  4. Do not treat an unlisted branch as fixed merely because the record does not identify it as affected. The status of unverified branches remains unknown.

Detection

  • Inventory ASUS Router models and firmware branches, then compare them with the affected branches listed in affected_summary.
  • Review system logs on affected devices for DDNS credentials or similar sensitive data.
  • Audit authenticated high-privilege accounts, especially accounts that can access logs or change router settings from an adjacent network.
  • Review DNS setting changes and DDNS configuration changes against approved administrative activity.
  • No specific IOC or log signature is provided. The absence of suspicious log entries does not prove that a device is safe.
Sources (12)
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.