CVE-2025-15605

Hardcoded Cryptographic Key in Configuration Encryption Mechanism on TP-Link Archer NX200, NX210, NX500 and NX600

HIGH
7.3
CVSS Score
Published: March 23, 2026 at 06:02 PM UTC
Updated: June 17, 2026 at 08:38 AM UTC
8 products affected across 1 vendorArcher NX500 FirmwareArcher NX200 FirmwareArcher NX600 Firmware

Using Archer NX600 v3.0 by TP-Link Systems Inc.?

Get instant alerts when new vulnerabilities affect Archer NX600 v3.0 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.3
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.3.0v < 1.8.0
tp-link-archer-nx200 (same device)
v < 1.3.0
tp-link-archer-nx210 (same device)
v < 1.3.0v < 1.5.0
tp-link-archer-nx500 (same device)
v < 1.3.0v < 1.4.0
tp-link-archer-nx600 (same device)
v < 1.3.0 Build 260311v < 1.8.0 Build 260311v < < 1.3.0 Build 260309
Affected range stops below 1.3.0 Build 260311, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.8.0 Build 260311, so it looks safe — our inference, not a vendor statement
Affected range stops below < 1.3.0 Build 260309, so it looks safe — our inference, not a vendor statement
v < 1.3.0 Build 260309v < 1.3.0 Build 260311
Affected range stops below 1.3.0 Build 260309, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.3.0 Build 260311, so it looks safe — our inference, not a vendor statement
v < 1.3.0 Build 260311v < < 1.5.0 Build 260309
Affected range stops below 1.3.0 Build 260311, so it looks safe — our inference, not a vendor statement
Affected range stops below < 1.5.0 Build 260309, so it looks safe — our inference, not a vendor statement
v < 1.3.0 Build 260309v < 1.3.0 Build 260311v < 1.4.0 Build 260311
Affected range stops below 1.3.0 Build 260309, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.3.0 Build 260311, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.4.0 Build 260311, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-321CWE-798

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card