Quick answers
- Is CVE-2026-102813 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102813 being exploited in the wild.
- How severe is CVE-2026-102813?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- TP-Link RE305 V3.
- Is there a fix for CVE-2026-102813?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-102813 attacked?
- It is attacked with local access or from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-102813?
- Check whether you run TP-Link RE305 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An unauthenticated attacker on the local network can trigger password-reset verification-code generation through an inadequately protected interface. The verification-code mechanism lacks rate-limiting or lockout, and uses predictable code generation, allowing the attacker to brute-force or obtain the code to reset the administrator password and access privileged device-management functions.
Affected products
- TP-Link RE305 V3
Timeline
- 2026-10-27: disclosed