# CVE-2026-6194: Totolink A3002MU HTTP Request formWlanSetup sub_410188 stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the HTTP request handler of Totolink A3002MU routers, potentially leading to arbitrary code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-wcjg-f74r-f452

## What is CVE-2026-6194?

CVE-2026-6194 is a high-severity memory corruption vulnerability in Totolink A3002MU, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in Totolink A3002MU B20211125.1046. Affected by this vulnerability is the function sub_410188 of the file /boafrm/formWlanSetup of the component HTTP Request Handler. This manipulation of the argument wan-url causes stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.

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-6194?


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

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

## Is CVE-2026-6194 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6194 is a high-severity memory corruption vulnerability in Totolink A3002MU, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6194 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-6194/ (Markdown: https://insights.sbomify.com/CVE-2026-6194/index.md)
```

## Sources

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

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