# CVE-2026-105285: Totolink A3002MU QoS Rule formIpQoS stack-based overflow

> Remote attackers can execute arbitrary code on Totolink A3002MU routers via a stack-based buffer overflow in the QoS Rule Handler.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-x79h-v8f2-79c8

## What is CVE-2026-105285?

CVE-2026-105285 is a critical memory corruption vulnerability in Totolink A3002MU, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been detected in Totolink A3002MU 1.0.0-B20230403.1455. This affects an unknown function of the file /boafrm/formIpQoS of the component QoS Rule Handler. The manipulation of the argument addQos/comment/entry_name leads to stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-105285 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105285 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105285 is a critical memory corruption vulnerability in Totolink A3002MU, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105285 exists.

Affected product: Totolink A3002MU. 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-105285/ (Markdown: https://insights.sbomify.com/CVE-2026-105285/index.md)
```

## Sources

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

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