# CVE-2026-93489: Improper Authentication in ASUS router modules allows an unauthenticated nearby user to send an HTTP request and forge an access ticket, sub


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-2wjj-2fhp-gff4

## What is CVE-2026-93489?

CVE-2026-93489 is a high-severity vulnerability in ASUS Router, published on 23 Oct 2026. 

### Official description

Improper Authentication in ASUS router modules allows an unauthenticated nearby user to send an HTTP request and forge an access ticket, subsequently enabling the user to perform administrator operations.
Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-93489 being exploited?

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

Public exploit code:

- https://github.com/cybersecurity/CVE-2026-93489 (github_poc): https://github.com/cybersecurity/CVE-2026-93489

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93489 is a high-severity vulnerability in ASUS Router, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93489 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-93489/ (Markdown: https://insights.sbomify.com/CVE-2026-93489/index.md)
```

## Sources

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

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