# CVE-2026-13313: Security feature bypass in Router

> Authenticated attackers can bypass security controls to enable Telnet and execute arbitrary commands with root privileges on ASUS routers.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-m5g8-55x2-4988

## What is CVE-2026-13313?

CVE-2026-13313 is a high-severity vulnerability in ASUS Router, published on 1 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An Active Debug Code vulnerability in certain ASUS router models allows a remote authenticated user, via a crafted HTTP request, to bypass security mechanisms and enable the Telnet service, thereby executing arbitrary commands with root privileges and potentially affecting other devices connected to the router.
Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.

Weakness: CWE-489 (Active Debug Code)

## Which versions are affected by CVE-2026-13313?


## How do I fix CVE-2026-13313?

No fix has been published for CVE-2026-13313 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13313 being exploited?

There is no known exploitation of CVE-2026-13313 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13313 and fix it if it is affected.

What it is: CVE-2026-13313 is a high-severity vulnerability in ASUS Router, published on 1 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13313 in the wild and no public exploit code.

Affected product: ASUS Router. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13313/ (Markdown: https://insights.sbomify.com/CVE-2026-13313/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13313
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13313
- OSV: https://osv.dev/vulnerability/CVE-2026-13313

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13313/
Summaries are generated and may contain mistakes; the official description above is the record.