# CVE-2026-26732: Memory corruption in n/a

> A stack-based buffer overflow in the formFilter function allows attackers to execute arbitrary code or cause denial of service on TOTOLINK routers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 Feb 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-pqh8-xq2x-mwg2

## What is CVE-2026-26732?

CVE-2026-26732 is a high-severity memory corruption vulnerability in n/a, published on 17 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TOTOLINK A3002RU V2.1.1-B20211108.1455 was discovered to contain a stack-based buffer overflow via the vpnUser or vpnPassword` parameters in the formFilter function.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Totolink A3002ru Firmware.

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

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

## Is CVE-2026-26732 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-34198](https://insights.sbomify.com/CVE-2024-34198/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-35491](https://insights.sbomify.com/CVE-2022-35491/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-19825](https://insights.sbomify.com/CVE-2019-19825/): Security feature bypass in n/a (critical 9.8)
- [CVE-2018-13306](https://insights.sbomify.com/CVE-2018-13306/): Command injection in n/a (critical 9.8)
- [CVE-2018-13307](https://insights.sbomify.com/CVE-2018-13307/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26732 is a high-severity memory corruption vulnerability in n/a, published on 17 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26732 in the wild and no public exploit code.

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

## Sources

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

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