CVE-2026-17518 Buffer Copy without Checking Size of Input in certain ASUS router models allows an adjacent authenticated user to corrupt device operations
High 8.2
Published
Updated
Check this codebase for CVE-2026-17518 and fix it if it is affected.
What it is: CVE-2026-17518 is a high-severity vulnerability in ASUS Router, published on 20 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-17518 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-17518/ (Markdown: https://insights.sbomify.com/CVE-2026-17518/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-17518?
CVE-2026-17518 is a high-severity vulnerability in ASUS Router, published on 20 Oct 2026.
Official description
Buffer Copy without Checking Size of Input in certain ASUS router models allows an adjacent authenticated user to corrupt device operations and cause a denial of service via an HTTP request with input exceeding the expected length. Refer to the ' Security Update for ASUS Router Firmware' section on the ASUS Security Advisory for more information.
Weakness: CWE-121
Which versions are affected by CVE-2026-17518?
How do I fix CVE-2026-17518?
No fix has been published for CVE-2026-17518 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-17518 being exploited?
There is no known exploitation of CVE-2026-17518 in the wild and no public exploit code.
Sources
Also known as GHSA-8j23-4jj7-m65q.