CVE-2026-102813: Administrator Password Reset Through the Verification-Code Interface in TP-Link RE305
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by TPLink, published 2026-10-27).
Weakness: CWE-338 Use of cryptographically weak Pseudo-Random number generator (PRNG)
How it can be exploited
Exploitable from an adjacent network with high attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality low, integrity high, availability low. 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
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.
Live scores
- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.048
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| TP-Link Systems Inc. RE305 v3 | before 1.1.8 Build 20260921 Rel. 42853 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 1.1.8 Build 20260921 Rel. 42853.
Vendor guidance:
- https://www.tp-link.com/us/support/download/re305/v3/#Firmware (patch)
- https://www.tp-link.com/en/support/download/re305/v3/#Firmware (patch)
- https://www.tp-link.com/us/support/faq/5362/ (vendor-advisory)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
- HKCERT reports multiple flaws in TP-Link Archer C7, C6, RE305 (full advisory)
References
Vendor advisories and patches
- https://www.tp-link.com/us/support/download/re305/v3/#Firmware (patch)
- https://www.tp-link.com/en/support/download/re305/v3/#Firmware (patch)
- https://www.tp-link.com/us/support/faq/5362/ (vendor-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners