# CVE-2026-102813: Administrator Password Reset Through the Verification-Code Interface in TP-Link RE305


- **Severity:** Medium 6.1 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-9q5p-8p59-jhwp

## What is CVE-2026-102813?

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

### Official description

An authentication flaw exists in the password-recovery functionality of TP-Link RE305 V3. The verification-code interface allows an unauthenticated attacker on the same local network to trigger generation of an administrator password-reset verification code. Because the interface lacks an effective attempt counter or lockout mechanism and uses a predictable verification-code generation process, an attacker may obtain or brute-force the code and reset the administrator password. 

Successful exploitation may allow an unauthenticated attacker on the local network to reset the administrator password and subsequently access privileged device-management functions.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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


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

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

## Is CVE-2026-102813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102813 is a medium-severity vulnerability in TP-Link Systems Inc. RE305 v3, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-102813 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-102813/ (Markdown: https://insights.sbomify.com/CVE-2026-102813/index.md)
```

## Sources

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

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