# CVE-2022-26988: Memory corruption in n/a

> A stack overflow in the MntAte function allows local users to achieve remote code execution on affected TP-Link, Mercury, and Fast routers.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-m682-89jg-jv7x

## What is CVE-2022-26988?

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

### Official description

TP-Link TL-WDR7660 2.0.30, Mercury D196G 20200109_2.0.4, and Fast FAC1900R 20190827_2.0.2 routers have a stack overflow issue in `MntAte` function. Local users could get remote code execution.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-26988?

It affects 6 products.


Products: Fastcom Fac1900r Firmware, Mercusys Mercury D196g Firmware, Tp-Link Tl-Wdr5660 Firmware, Tp-Link Tl-Wdr7620 Firmware, Tp-Link Tl-Wdr7660 Firmware, Tp-Link Tl-Wdr7661 Firmware.

## How do I fix CVE-2022-26988?

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

## Is CVE-2022-26988 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-26987](https://insights.sbomify.com/CVE-2022-26987/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26988 and fix it if it is affected.

What it is: CVE-2022-26988 is a high-severity memory corruption vulnerability in n/a, published on 10 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26988 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-2022-26988/ (Markdown: https://insights.sbomify.com/CVE-2022-26988/index.md)
```

## Sources

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

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