Quick answers
- Is CVE-2026-76653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76653 being exploited in the wild.
- How severe is CVE-2026-76653?
- Informational severity, published 10 September 2026.
- Which products and versions are affected?
- TP-Link Archer MR600 v2, v3, v5; TP-Link TL-MR6400 v8.
- Is there a fix for CVE-2026-76653?
- 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-76653 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-76653?
- Check whether you run TP-Link Archer MR600 or TP-Link TL-MR6400 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
The vulnerability is a missing authentication check in the VPN configuration management interface of affected TP-Link routers. The root cause is improper access control that allows unauthenticated remote attackers to read and modify VPN configuration information via direct API or web interface access. The vulnerability is network-reachable and requires no authentication or user interaction. Successful exploitation allows an attacker to view sensitive VPN credentials and configuration, or alter VPN settings to redirect or monitor traffic. Patch availability has not been disclosed in the advisory materials reviewed.
Affected products
- TP-Link Archer MR600 v2, v3, v5
- TP-Link TL-MR6400 v8
Timeline
- 2026-09-10: disclosed