# CVE-2026-0834: Logic Vulnerability on TP-Link Archer C20, Archer AX53 and TL-WR841N v13

> Unauthenticated adjacent attackers can execute administrative commands like factory reset and reboot on TP-Link routers, causing service disruption and configuration loss.

- **Severity:** High 7.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 21 Jan 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-cpr3-8r3m-jjf4

## What is CVE-2026-0834?

CVE-2026-0834 is a high-severity missing authorization vulnerability in TP Link Systems Inc. Archer C20 V5, published on 21 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Logic vulnerability in TP-Link Archer C20 v5, 6.0, Archer AX53 v1.0 and TL-WR841N v13 (TDDP module) allows unauthenticated adjacent attackers to execute administrative commands including factory reset and device reboot without credentials. Attackers on the adjacent network can remotely trigger factory resets and reboots without credentials, causing configuration loss and interruption of device availability.

This issue affects Archer C20 v6.0 < V6_251031, Archer C20 v5 <EU_V5_260317 or < US_V5_260419

Archer AX53 v1.0 < 

V1_251215

TL-WR841N v13 < 0.9.1 Build 20231120 Rel.62366

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 2 products.


Products: Tp-Link Archer Ax53 Firmware, Tp-Link Archer C20 Firmware.

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

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

## Is CVE-2026-0834 being exploited?

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

Public exploit code:

- Proof of Concept (PoC) for the TP-Link Device Debug Protocol (TDDP) Authentication Bypass (CVE-2026-0834) (github_poc): https://github.com/mattgsys/CVE-2026-0834

## Other vulnerabilities in TP Link Systems Inc. Archer C20 V5

- [CVE-2025-62673](https://insights.sbomify.com/CVE-2025-62673/): Heap-based Buffer Overflow Vulnerability in Archer AX53 and AX12 (high 8.6)
- [CVE-2026-30815](https://insights.sbomify.com/CVE-2026-30815/): OS Command Injection Vulnerability in OpenVPN Module in TP-Link AX53 (high 8.5)
- [CVE-2026-30818](https://insights.sbomify.com/CVE-2026-30818/): OS Command Injection Vulnerability in dnsmasq Module in TP-Link AX53 (high 8.5)
- [CVE-2025-15608](https://insights.sbomify.com/CVE-2025-15608/): Buffer Overflow in Network Probe Handling Function of TP-Link Archer AX53 + Archer AX55 (high 7.7)
- [CVE-2026-30814](https://insights.sbomify.com/CVE-2026-30814/): Buffer Overflow Vulnerability in TP-Link AX53 (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0834 is a high-severity missing authorization vulnerability in TP Link Systems Inc. Archer C20 V5, published on 21 Jan 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-0834 exists.

Affected product: TP Link Systems Inc. Archer C20 V5. 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-0834/ (Markdown: https://insights.sbomify.com/CVE-2026-0834/index.md)
```

## Sources

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

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