# CVE-2026-9105: Authenticated Stack-Based Buffer Overflow in TP-Link TL-WR841N Web Interface

> An authenticated attacker can trigger a stack buffer overflow in the TP-Link TL-WR841N web interface, causing a device crash and reboot.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/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:** 29 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-whjh-xgqc-hvvf

## What is CVE-2026-9105?

CVE-2026-9105 is a medium-severity memory corruption vulnerability in TP-Link Systems Inc. TL-WR841N v14, published on 29 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An authenticated stack-based buffer overflow vulnerability exists in the web management interface of TP-Link TL-WR841N v14.  A remote authenticated attacker can send crafted HTTP requests to cause the embedded web server to overflow a stack buffer, resulting in a crash of the affected process.

Successful exploitation results in a denial-of-service condition, causing the device to crash and automatically reboot.

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

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

It affects 1 product.


Products: Tp-Link Tl-Wr841n Firmware.

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

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

## Is CVE-2026-9105 being exploited?

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

## Other vulnerabilities in TP-Link Systems Inc. TL-WR841N v14

- [CVE-2022-25073](https://insights.sbomify.com/CVE-2022-25073/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-12575](https://insights.sbomify.com/CVE-2018-12575/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-46912](https://insights.sbomify.com/CVE-2022-46912/): File upload in n/a (high 8.8)
- [CVE-2020-35576](https://insights.sbomify.com/CVE-2020-35576/): Command injection in n/a (high 8.8)
- [CVE-2019-17147](https://insights.sbomify.com/CVE-2019-17147/): Memory corruption in TL-WR841N (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9105 is a medium-severity memory corruption vulnerability in TP-Link Systems Inc. TL-WR841N v14, published on 29 Jun 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-9105 in the wild and no public exploit code.

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

## Sources

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

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