Skip to navigation

Threat reportVulnerabilityTL-2026-1617

Critical ASUS Router Flaw (CVE-2026-13385) Enables MITM Arbitrary Command Execution

criticalPATCHED

CVE-2026-13385 (CVSS 4.0: 9.5, CRITICAL) is an improper integrity-check-value validation and improper certificate validation flaw in certain ASUS router firmware series (3.0.0.4_386, 3.0.0.4_388, 3.0.0.6_102) that allows a network-adjacent man-in-the-middle attacker to spoof a firmware/update server and trick the router into downloading and executing arbitrary commands.

Key facts

IdentifiersTL-2026-1617, CVE-2026-13385
SeverityCRITICAL
CVSS9.5 (CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H)
EPSSCVE-2026-13385: 0.1% (2.9th percentile)
Affected productsASUS Router (multiple models sharing affected firmware series)
Weaknesses (CWE)CWE-295, CWE-354
MITRE ATT&CK techniquesT1046 Network Service Discovery, T1059 Command and Scripting Interpreter, T1090 Proxy, T1102 Web Service, T1190 Exploit Public-Facing Application, T1203 Exploitation for Client Execution, T1210 Exploitation of Remote Services, T1498 Network Denial of Service, T1553 Subvert Trust Controls, T1554 Compromise Host Software Binary, T1556 Modify Authentication Process, T1557 Adversary-in-the-Middle and 3 more in the attack flow
MotivationUNKNOWN
Target sectorsconsumer, smallofficehomeoffice, telecoms, criticalinfrastructureedge
Target regionsGlobal
Detection rules9 (1 shown free)
Sources12 cited sources

Detection coverage

As of 2026-07-22, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1617 across Splunk SPL, Microsoft KQL and Sigma, covering 16 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: ASUS Router TLS Certificate Validation Bypass on Update Channel (CVE-2026-13385)

Detects a firmware/config update or cloud-sync TLS handshake on a network device where certificate validation failed (self-signed, hostname mismatch, or untrusted CA) but the connection was accepted anyway — the CWE-295 precondition attackers exploit via CVE-2026-13385 to spoof the ASUS update server in a MITM position.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1557, T1190
  • Data sources: network_devices, firewall_tls_inspection_logs, router_syslog
  • Severity: critical
  • Confidence: high

Splunk SPL

index=network_devices sourcetype="asus:router:tls" OR sourcetype="firewall:tls_inspection"
| eval cert_validation_result=coalesce(cert_validation_result, tls_verify_result)
| where cert_validation_result IN ("failed", "self-signed", "hostname_mismatch", "untrusted") AND connection_outcome="accepted"
| where dest_port=443 OR dest_port=9443
| stats count min(_time) as first_seen max(_time) as last_seen values(dest_ip) as dest_ips values(cert_validation_result) as cert_issues by src_ip, dest_ip
| where count > 0
| table src_ip, dest_ip, dest_ips, cert_issues, count, first_seen, last_seen

Microsoft KQL

DeviceNetworkEvents
| where Timestamp > ago(24h)
| where RemotePort in (443, 9443)
| where ActionType == "TlsCertificateValidationFailed" or AdditionalFields has "cert_validation_result"
| extend CertResult = tostring(parse_json(AdditionalFields).cert_validation_result)
| where CertResult in ("failed", "self-signed", "hostname_mismatch", "untrusted")
| extend ConnectionOutcome = tostring(parse_json(AdditionalFields).connection_outcome)
| where ConnectionOutcome == "accepted"
| project Timestamp, DeviceName, LocalIP, RemoteIP, RemoteUrl, CertResult, ConnectionOutcome
| summarize count(), min(Timestamp), max(Timestamp) by DeviceName, RemoteIP

Sigma

title: Router Firmware/Config Update Client Accepted Invalid TLS Certificate
id: a1b2c3d4-1111-4a1a-9a11-cve202613385s1
status: experimental
description: Detects a network device update/sync client accepting a TLS session despite failed certificate validation, the CWE-295 precondition for CVE-2026-13385 MITM exploitation.
references:
    - CVE-2026-13385
    - https://gbhackers.com/critical-asus-router-flaw/
author: Threadlinqs Team
date: 2026-07-22
tags:
    - attack.initial_access
    - attack.t1557
    - attack.t1190
    - cve.2026.13385
logsource:
    category: application
    product: network_device
detection:
    selection:
        EventType: 'tls_handshake'
        cert_validation_result:
            - 'failed'
            - 'self-signed'
            - 'hostname_mismatch'
            - 'untrusted'
        connection_outcome: 'accepted'
    condition: selection
falsepositives:
    - Legitimate self-signed lab/test environments intentionally configured for internal update servers
    - Misconfigured but benign internal cert infrastructure
level: critical

Known false positives:

  • Legitimate self-signed lab/test environments intentionally configured for internal update servers
  • Misconfigured but benign internal certificate infrastructure not related to exploitation

Tuning notes: Scope to known ASUS router management VLANs/subnets and exclude approved internal PKI CAs from the untrusted-cert alert list; correlate with dest_port 443/9443 to reduce noise from unrelated TLS inspection events.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Root Certificate / Trust Store Modification on Network Management Host (CVE-2026-13385 AitM Enablement) · unlock with TL Creds
  • Persistence Artifact Created by Router Update/Sync Client Process (CVE-2026-13385 Post-Exploitation) · unlock with TL Creds
  • DNS Server / WAN Configuration Change Shortly After Untrusted Network Connection (CVE-2026-13385 DNS Hijack Indicator) · unlock with TL Creds
  • Reconnaissance Scanning for Vulnerable ASUS Firmware Series (CVE-2026-13385 Pre-Positioning) · unlock with TL Creds
  • Exploit Public-Facing Application via Spoofed Update Server Payload Delivery (CVE-2026-13385) · unlock with TL Creds
  • Router Recruited into Proxy/Botnet Infrastructure Post-Exploitation (CVE-2026-13385 C2 Indicator) · unlock with TL Creds
  • Router Update-Client Payload Accepted Without Integrity Check (CVE-2026-13385) · unlock with TL Creds
  • Router Command Execution Immediately Following Spoofed Update-Server Connection (CVE-2026-13385) · unlock with TL Creds

Indicators of compromise

As of 2026-07-22, Threadlinqs Intelligence tracks 16 indicators of compromise for TL-2026-1617.

16 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

ASUS has released patched firmware; no public PoC or confirmed active exploitation has been reported.

CVE-2026-13385 is a critical improper-validation vulnerability affecting certain ASUS router firmware builds in the 3.0.0.4_386, 3.0.0.4_388, and 3.0.0.6_102 series. The root cause is dual: (1) CWE-354 Improper Validation of Integrity Check Value — the router firmware/update or configuration-sync client does not correctly validate a cryptographic integrity check (e.g. checksum/signature) on data received from a remote server, and (2) CWE-295 Improper Certificate Validation — the same client fails to properly validate the TLS certificate presented by that remote server. Combined, these defects mean the router's update/sync mechanism can be tricked into trusting a server that is not the legitimate ASUS/cloud endpoint, provided the attacker can position themselves as a man-in-the-middle (MITM) on the network path between the router and that server — e.g. via ARP/DNS spoofing on the LAN, a rogue access point, a compromised upstream ISP hop, or interception on an untrusted network the router's WAN traverses.

An attacker who achieves this MITM position can stand up a spoofed server that mimics the expected update/response payload. Because the router does not verify server identity (invalid/self-signed/mismatched certificate accepted) and does not verify payload integrity (a manipulated or unsigned blob passes the check), the spoofed server can supply a malicious payload that the router downloads and executes as a command — i.e., the flaw provides a direct path from network-level interception to command execution on the device, with no user interaction and no authentication required (CVSS 4.0 vector: AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H — network vector, low complexity, attack requirements present [MITM position needed], no privileges, no user interaction, high impact to confidentiality/integrity/availability of both the vulnerable system and any subsequent system it can reach).

Post-exploitation impact on a compromised SOHO/consumer router is severe given its position as the network's default gateway: full device takeover, persistent implant/backdoor installation, DNS hijacking of every downstream client, further traffic interception (defeating the very trust boundary the router is meant to protect), pivoting to internal LAN hosts, and recruitment into a router/IoT botnet for DDoS or proxy (residential-proxy / anonymization) infrastructure — impact patterns consistent with historical ASUS router compromise campaigns (e.g. the 2025 GreyNoise-documented stealthy ASUS backdoor campaign affecting thousands of devices, which is a separate incident/CVE but illustrates the exploitation ceiling for this device class).

As of this writing there is no public proof-of-concept exploit code and no confirmed in-the-wild exploitation; the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. ASUS has already shipped patched firmware for the affected series and — per its Product Security Incident Response practice, which follows ISO/IEC 29147:2018 (vulnerability disclosure) and ISO/IEC 30111:2019 (vulnerability handling) — strongly advises all affected-model owners to update immediately. Because exploitation requires a MITM position, the primary practical exposure window is for devices whose WAN/administrative traffic traverses untrusted or attacker-influenced network segments before the firmware update is applied.

MITRE ATT&CK techniques by tactic:

Discovery

T1046 Network Service Discovery

Execution

T1059 Command and Scripting Interpreter; T1203 Exploitation for Client Execution

Command and Control

T1090 Proxy; T1102 Web Service

Initial Access

T1190 Exploit Public-Facing Application

Lateral Movement

T1210 Exploitation of Remote Services

Impact

T1498 Network Denial of Service; T1565 Data Manipulation

defense-impairment

T1553 Subvert Trust Controls

Persistence

T1554 Compromise Host Software Binary; T1556 Modify Authentication Process

credential-access

T1557 Adversary-in-the-Middle

Credential Access

T1557 Adversary-in-the-Middle

Collection

T1557 Adversary-in-the-Middle

Resource Development

T1584 Compromise Infrastructure

Reconnaissance

T1595 Active Scanning

Remediation

Patches

  • Apply the ASUS Security Advisory firmware update for CVE-2026-13385 (see ASUS Security Advisory portal, asus.com/security-advisory)

Immediate actions

  • Update all affected ASUS router models to the patched firmware release addressing CVE-2026-13385
  • Avoid connecting the router's WAN interface or administrative sessions to untrusted or public networks where a MITM position is achievable until patched
  • Restrict/disable remote administration and any cloud-sync/auto-update client where feasible while awaiting patch confirmation
  • Verify current firmware version against the affected series (3.0.0.4_386, 3.0.0.4_388, 3.0.0.6_102) via the router admin UI

Workarounds

  • If immediate patching is not possible, disable remote/cloud-based firmware update and configuration-sync features and perform manual, verified firmware installation from the official ASUS support site

Longer-term hardening

  • Enforce certificate pinning / strict TLS validation for all device-to-cloud and firmware-update channels
  • Cryptographically sign and verify update payloads with a robust integrity check independent of TLS trust
  • Deploy network segmentation isolating router management interfaces from general LAN/WAN traffic
  • Monitor router DNS and outbound configuration for unauthorized changes indicative of MITM tampering
  • Maintain an asset inventory of ASUS router models/firmware versions to accelerate future patch rollouts

Affected and fixed versions

  • ASUS — Router (multiple models sharing affected firmware series)
    Vulnerable versions: 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102
    Fixed in: Patched firmware released by ASUS post-2026-07-15 addressing CVE-2026-13385 (see ASUS Security Advisory for model-specific build numbers)

Timeline

  • CVE-2026-13385 identifier reserved by MITRE's CVE Numbering Authority process, roughly three weeks ahead of public disclosure.
  • Threat-intelligence aggregators (OffSeq Threat Radar, TheHackerWire) publish technical summaries of CVE-2026-13385 including CWE mapping and CVSS v4.0 vector.
  • INCIBE-CERT publishes an early-warning advisory for CVE-2026-13385, confirming CVSS 9.5 CRITICAL classification and affected firmware series.
  • CVE-2026-13385 published by MITRE/NVD, describing an Improper Validation of Integrity Check Value (CWE-354) and Improper Certificate Validation (CWE-295) flaw in certain ASUS router models.
  • CVE-2026-13385 record last modified in NVD with refined CVSS v4.0 scoring (9.5, CRITICAL).
  • ASUS firmware patches for the affected 3.0.0.4_386, 3.0.0.4_388, and 3.0.0.6_102 series are available at time of disclosure; ASUS advises immediate update via its Security Advisory portal.
  • Threat ingested into the TL-Intel Harness backlog via the GBHackers RSS feed for hunt/research processing (TL-2026-1617).
  • GBHackers publishes a public-facing article summarizing the vulnerability, its MITM/command-execution impact, and ASUS's patch guidance.
  • NVD/aggregator tracking (OffSeq Threat Radar) shows a further record update on the public-disclosure date, coinciding with GBHackers media coverage.

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 12 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats