CVE-2023-27359 is a race condition in the hotplugd daemon of the TP-Link Archer AX21 router. It can expose LAN-side services to remote attackers, and NVD scores it 8.1, High. The Zero Day Initiative says TP-Link has issued a firmware update. Install it on every AX21 you manage.
What's affected
NVD lists the Archer AX21 hardware version 3.0 and firmware 1.1.1 build 20220603 as affected. The Zero Day Initiative advisory names the product as the AX1800 and refers to the Archer AX21, and it links to TP-Link's firmware downloads for the AX21 v3.
I could not find a specific fixed firmware number in the sources I read. The advisory says only that TP-Link has issued an update. Check the AX21 v3 download page on TP-Link's site for the current build, and treat anything older than the latest as suspect until you have read its release notes.
No conflict on severity: the record scores the issue 8.1 High with a high attack complexity, and the advisory I read gives no separate score.
How to check if you're exposed
Open the router's admin page and read the firmware version under the system or about section. Compare it with the latest build on TP-Link's download page for your exact hardware version. The hardware revision is printed on the label under the router, and the v3 label matters because firmware is specific to it.
If you cannot log in to the device, assume it is out of date and plan an update window. Also check whether remote management is switched on, since the record describes a remote attacker.
What to do now
- Download the latest firmware for the Archer AX21 v3 from TP-Link's support site and install it. Follow the release notes.
- Confirm the router's remote management feature is off unless you need it.
- Check that any services on the LAN side, such as file shares or admin pages, also have their own passwords. The flaw is about reaching resources meant only for the LAN.
- Add the AX21 to your asset list with its firmware version.
- Follow the Gold page for this CVE for any change in score or references.
Why it matters
The record says firewall rule handling lets an attacker reach resources that should be available to the LAN interface only. The weakness class is CWE-362 (Race Condition). In a race condition, two actions happen close together and the outcome depends on which one wins. Here the window lets traffic through before the firewall rule is in place.
NVD notes that an attacker can combine this with other vulnerabilities to run code as root. That is why the issue matters even though the complexity is high. It is a way past the perimeter, and the services behind it often trust anyone on the inside.
Quick check
Does this need a login?
No. The record says authentication is not required, but the attack complexity is rated high.
Sources
Last reviewed: 19 October 2026.