# CVE-2026-84729: CVE-2026-84729

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

Out-of-bounds write in certain ASUS Router firmware allow an unauthenticated nearby attacker to write data beyond the intended buffer or potentially cause a denial-of-service (DoS) via a crafted packet.
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: ASUSWRT 3.0.0.4_386 series (affected, custom); ASUSWRT 3.0.0.4_388 series (affected, custom); ASUSWRT 3.0.0.6_102 series (affected, custom). Source: CNA: ASUS

## Severity and prioritization

- CVSS 4.0: 7.2 (high); CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/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-787

## 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-84729; retrieved 2026-11-04; source updated 2026-11-04

Revision: 1665594c8253b9449c6c69427b97467330235d78797ef4d6bc5c221b827639e6

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

## 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.