# CVE-2026-17250: Authenticated Remote Code Execution via Stack-Based Buffer Overflow in Firmware Update Handling

> An authenticated attacker can execute arbitrary code on TP-Link TL-MR6400 v7 routers via a stack-based buffer overflow in firmware update handling.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-82fj-885j-3xg6

## What is CVE-2026-17250?

CVE-2026-17250 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. TL-MR6400 v7.0, published on 21 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A
stack-based buffer overflow vulnerability exists in the firmware update
functionality of TL-MR6400 v7 due to unsafe processing of
attacker-controlled metadata within a firmware image. 

Successful
exploitation may allow an authenticated attacker to trigger memory corruption
and execute arbitrary code on the affected device.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-17250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17250 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. TL-MR6400 v7.0, published on 21 Aug 2026. 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-2026-17250 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. TL-MR6400 v7.0. 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-17250/ (Markdown: https://insights.sbomify.com/CVE-2026-17250/index.md)
```

## Sources

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

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