# CVE-2026-102814: Improper Authentication in TP-Link TDDP v2 Allows Root Command Execution in TP-Link RE305


- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-7pqg-m5f8-c886

## What is CVE-2026-102814?

CVE-2026-102814 is a high-severity vulnerability in TP-Link Systems Inc. RE305 v3, published on 27 Oct 2026. 

### Official description

An
authentication weakness exists in the TP-Link TDDP v2 service of TP-Link RE305
V3. TDDP v2 uses a fixed and derivable cryptographic key, which may allow an
unauthenticated attacker on the same local network to forge protocol packets
and access privileged TDDP operations, including functionality that can lead to
operating-system command execution when the TDDP service is running and
accessible.

Successful
exploitation may allow an unauthenticated attacker on the same local area
network to execute arbitrary system commands with root privileges.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-102814 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102814 is a high-severity vulnerability in TP-Link Systems Inc. RE305 v3, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-102814 in the wild and no public exploit code.

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

## Sources

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

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