A hard‑coded cryptographic key embedded in the firmware’s configuration encryption routine allows anyone with device credentials to decrypt, alter, and re‑encrypt configuration data. The flaw exposes both the confidentiality of stored settings and the integrity of configuration controls, meaning an authenticated attacker can modify routing tables, firewall rules, or other critical parameters without needing to compromise the underlying hardware. The static key weakness is classified as CWE‑321 and CWE‑798.

The vulnerability affects TP‑Link Archer routers across several models: Archer NX200 versions 1.0, 2.0, 2.20, and 3.0; Archer NX210 versions 2.0, 2.20, and 3.0; Archer NX500 versions 1.0 and 2.0; and Archer NX600 versions 1.0, 2.0, and 3.0. All listed firmware releases from these devices are impacted.

The CVSS base score of 8.5 indicates a high‑severity flaw, yet the EPSS score is below 1%, suggesting that automated exploitation is unlikely but not impossible. The vulnerability is not currently cataloged in CISA’s KEV list. Because it requires authentication, an attacker must first obtain valid user credentials or take advantage of a local management interface, making the risk contingent on device access controls. Once authenticated, the attacker can tamper with configuration data, potentially redirecting traffic, disabling security features, or creating persistence mechanisms within the router.