CVE-2026-9817 A stack-based buffer overflow vulnerability exists in the boa formUploadFile functionality of X2000R (version(s): TOTOLINK-X2000R-Gh-V1.0.0-B20250421.1327).
Critical 9.1
Published
Updated
Check this codebase for CVE-2026-9817 and fix it if it is affected.
What it is: CVE-2026-9817 is a critical vulnerability in Totolink, published on 20 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-9817 in the wild and no public exploit code.
Affected product: Totolink. 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-9817/ (Markdown: https://insights.sbomify.com/CVE-2026-9817/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-9817?
CVE-2026-9817 is a critical vulnerability in Totolink, published on 20 Oct 2026.
Official description
A stack-based buffer overflow vulnerability exists in the boa formUploadFile functionality of X2000R (version(s): TOTOLINK-X2000R-Gh-V1.0.0-B20250421.1327). A specially crafted HTTP request can lead to arbitrary code execution. An attacker can make an authenticated HTTP request to trigger this vulnerability.
Weakness: CWE-121
Which versions are affected by CVE-2026-9817?
How do I fix CVE-2026-9817?
No fix has been published for CVE-2026-9817 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-9817 being exploited?
There is no known exploitation of CVE-2026-9817 in the wild and no public exploit code.
Sources
Also known as GHSA-4x89-c5gq-3rg8.