Skip to main content
CISA Known Exploited Vulnerabilities

ASUS RT-AX55 Routers OS Command Injection Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2025-06-02
Remediation due
2025-06-23

Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes
https://www.asus.com/networking-iot-servers/wifi-6/all-series/rt-ax55/helpdesk_bios/?model2Name=RT-AX55 ; https://www.asus.com/content/asus-product-security-advisory/ ; https://nvd.nist.gov/vuln/detail/CVE-2023-39780

Description

On ASUS RT-AX55 3.0.0.4.386.51598 devices, authenticated attackers can perform OS command injection via the /start_apply.htm qos_bw_rulelist parameter. NOTE: for the similar "token-generated module" issue, see CVE-2023-41345; for the similar "token-refresh module" issue, see CVE-2023-41346; for the similar "check token module" issue, see CVE-2023-41347; and for the similar "code-authentication module" issue, see CVE-2023-41348.

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2023-39780 to the KEV catalog 630 days after its CVE record was published. The median for entries added in 2025 is 26 days.
  • It is one of 3 ASUS entries in the CISA KEV catalog, and one of 3 added in 2025.
  • Its current EPSS score (39.5%) is higher than that of 44% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score8.8 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableno
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
and forensic triage
Asset not publicly exposed
14 days
KEV due date
2025-06-23
21 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2025-06-06).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
ASUS
RT-AX55
3.0.0.4.386.51598

More from ASUS

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.