# CVE-2026-126724: CVE-2026-126724

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

Rooxis RXR-12 Wi-Fi router contains an undocumented UID-0 backdoor account (dg) with a firmware-wide default password (ivanlee) and interactive shell (/bin/ash), allowing authentication as root via SSH or local console without device-specific secrets. Firmware 20260813_c2169ea5 removes the account from the shipped root filesystem and disables root password authentication in SSH. Users can update their router can be through the local web interface.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Rooxis / Rooxis RXR-12: ≥ 0; < 20260813_c2169ea5 (affected, custom). Source: CNA: certcc

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-798

## Exploit evidence

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

## References

- https://rooxis.com/firmware/SOP-ramips-mt7621-DGR7-ROOXIS-local-debug.bin (CNA: certcc)

- https://lab.geodesy.phd/writeups/rooxis-router/ (CNA: certcc)

- https://lab.geodesy.phd/writeups/rooxis-router/ (cret@cert.org)

- https://rooxis.com/firmware/SOP-ramips-mt7621-DGR7-ROOXIS-local-debug.bin (cret@cert.org)

## Provenance

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

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126724; retrieved 2026-11-11; source updated 2026-11-11

Revision: 5fd445f6f52827d4b0d64671c44ec09ba0bebb5cec51fa1bf19ee4e4b4e3ad75

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

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