TP-Link TL Wr886n Vulnerabilities
39 known CVEs, 24 critical. Last updated 2026-10-24.
Known CVEs
TP-Link TL-WR886N 7.0 1.1.0 devices allow remote attackers to cause a denial of service (Tlb Load Exception) via crafted DNS packets to port 53/udp.
A Buffer Overflow vulnerability exists in TP-LINK WR-886N 20190826 2.3.8 in the /cloud_config/router_post/check_reg_verify_code function which could let a remove malicious user execute arbitrary code via a crafted pos...
A Buffer Overflow vulnerability exists in TP-LINK WR-886N 20190826 2.3.8 via the /cloud_config/router_post/check_reset_pwd_verify_code interface.
A Buffer Overflow vulnerability exists in TP-LINK WR-886N 20190826 2.3.8 in /cloud_config/cloud_device/info interface, which allows a malicious user to executee arbitrary code on the system via a crafted post request.
A Buffer Overflow vulnerability exists in TP-LINK WR-886N 20190826 2.3.8 in the /cloud_config/router_post/get_reg_verify_code feature, which allows malicious users to execute arbitrary code on the system via a crafted...
A Buffer Overflow vulnerability exists in TP-LINK WR-886N 20190826 2.3.8 in the /cloud_config/router_post/get_reset_pwd_veirfy_code feature, which allows malicious users to execute arbitrary code on the system via a c...
A Buffer Overflow vulnerabiltiy exists in TP-LINK WR-886N 20190826 2.3.8 in thee /cloud_config/router_post/login feature, which allows malicious users to execute arbitrary code on the system via a crafted post request.
A Buffer Overflow vulnerabilitiy exists in TP-LINK WR-886N 20190826 2.3.8 in the /cloud_config/router_post/register feature, which allows malicious users to execute arbitrary code on the system via a crafted post requ...
A Buffer Overflow vulnerability exists in TP-LINK WR-886N 20190826 2.3.8 in the /cloud_config/router_post/modify_account_pwd feature, which allows malicious users to execute arbitrary code on the system via a crafted ...
A Buffer Overflow vulnerability exists in TP-LINK WR-886N 20190826 2.3.8 in the /cloud_config/router_post/reset_cloud_pwd feature, which allows malicous users to execute arbitrary code on the system via a crafted post...
Commonly exposed ports
- Port 23 (Telnet) — Sends admin credentials unencrypted — a common target on older router firmware.
- Port 80 (HTTP admin panel) — The web admin UI; dangerous if remote/WAN administration is left enabled.
- Port 7547 (TR-069 (CWMP)) — ISP remote-management protocol — has been the entry point for several router botnets.
- Port 1900 (UPnP/SSDP) — Lets apps on your LAN open firewall holes automatically, sometimes without your knowledge.
Default credentials
From ProbeShield's own tested default-credential list (see probeshield.com/default-passwords/): "admin" / "tplink" or "admin" / "admin123" over HTTP.
Hardening checklist
- Disable remote (WAN-side) administration unless you specifically need it.
- Turn off UPnP unless a specific app you trust requires it.
- Turn off WPS — it can let an attacker bypass your Wi-Fi password.
- Change the default admin username and password to something unique.
- Check for a firmware update in the router’s admin panel and apply it.
- Disable Telnet/SSH management access if you don’t actively use it.
Frequently asked questions
Is my TP-Link TL Wr886n affected by these vulnerabilities? Only if you’re running a firmware version in the affected range listed above and haven’t updated. Check your router's admin panel for its current firmware version and compare it against the ranges below.
How do I update my TP-Link TL Wr886n's firmware? Log into the router's web admin panel (usually at its local IP address) and look for a Firmware Update or System Update section, or use the vendor's mobile app if it has one.
Does ProbeShield fix these vulnerabilities for me? No — ProbeShield scans your network and tells you what it finds (open ports, default credentials, outdated firmware signals) so you know what to fix, and how. It never changes your devices’ settings.
Sources: National Vulnerability Database (NVD), CISA Known Exploited Vulnerabilities Catalog. This page lists which firmware versions are affected — it doesn't claim your specific unit is vulnerable. Check your device's current firmware version in its admin panel and compare it against the ranges above.