# CVE-2026-88710: CVE-2026-88710

Status: published. Published: 2026-11-10. Updated: 2026-11-10.

Improper
neutralization of special elements used in an OS command in certain
ASUS Router firmware
allows an unauthenticated nearby user to trigger a chain of
actions—unauthenticated queries, identifier guessing, credential overwriting,
and command injection—resulting in the execution of arbitrary commands with
root privileges.
Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- ASUS / Router firmware: 3.0.0.4.386 series (affected, custom); 3.0.0.4.388 series (affected); 3.0.0.6.102 series (affected). Source: CNA: ASUS

## Severity and prioritization

- CVSS 4.0: 8.7 (high); CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N; source: CNA: ASUS

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-78

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.asus.com/security-advisory (CNA: ASUS)

## Provenance

- CNA: ASUS: https://www.cve.org/CVERecord?id=CVE-2026-88710; retrieved 2026-11-10; source updated 2026-11-10

Revision: bf344d5e8c6a3aedb504e72c16ab75e8c75a4ec04d6197bd15d800738e0d1c2b

Canonical: https://y2.dev/cve/CVE-2026-88710

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.