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

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

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-5jg4-px58-ghq6

## What is CVE-2026-26736?

CVE-2026-26736 is a high-severity memory corruption vulnerability in n/a, published on 17 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TOTOLINK A3002RU_V3 V3.0.0-B20220304.1804 was discovered to contain a stack-based buffer overflow via the static_ipv6 parameter in the formIpv6Setup function.

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

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

It affects 1 product.


Products: Totolink A3002ru Firmware.

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

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

## Is CVE-2026-26736 being exploited?

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

## 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-26736 and fix it if it is affected.

What it is: CVE-2026-26736 is a high-severity memory corruption vulnerability in n/a, published on 17 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26736 exists.

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-26736/ (Markdown: https://insights.sbomify.com/CVE-2026-26736/index.md)
```

## Sources

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

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