Skip to main content

TP-Link Archer C6 CVE-2026-89052

| EUVDEUVD-2026-107666 MEDIUM
Use of Hard-coded Cryptographic Key (CWE-321)
2026-10-21 TPLink GHSA-9cmp-4hhr-2px3
5.9
CVSS 4.0 · Vendor: TPLink
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain admin access to export configuration
  2. Exploit
    Obtain encrypted configuration or credential file
  3. Execution
    Decrypt offline using hardcoded universal key
  4. Impact
    Recover plaintext administrative credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
Exploitation Conditions

Exploitation requires the attacker to possess the encrypted artifact itself: an exported Archer C6 V2 configuration backup file or other protected credential data stored by the device. The hardcoded, device-universal cryptographic key then decrypts it, exposing plaintext administrative credentials. Limiting factors: the CVSS vector specifies PR:H, so administrative access is normally needed to generate/export the encrypted config, and AT:P reflects the requirement to first acquire that file - a remote, unauthenticated attacker cannot decrypt credentials without obtaining the protected data through a backup leak, support/RMA channel, or prior compromise. Because the key is shared across all devices, once any one config file is obtained the same key decrypts files from every Archer C6 V2 unit.

Impact

This is a moderate-severity confidentiality issue (CVSS 4.0 base 5.9) rather than a top-priority emergency. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N) is internally telling: although attack vector is marked Network, it carries both PR:H (high privileges required) and AT:P (a specific attack requirement - the attacker must first obtain the encrypted configuration or protected credential data). Those two gating conditions are what hold the score below 6.0 despite a High confidentiality impact. No EPSS score, KEV listing, or POC was provided in the input, so exploitation likelihood signals are absent: per precision rules this is 'no public exploit identified at time of analysis,' which should NOT be read as proof of safety - it reflects missing data, not confirmed absence of exploit code. The practical risk is bounded: the flaw is a classic hardcoded/universal cryptographic key (CWE-321) that makes any obtained encrypted config trivially decryptable across the entire device fleet, so the real danger materializes only after an attacker already holds the protected file (e.g., via a leaked backup, support upload, or secondary compromise). Note a mild internal tension: AV:N implies remote exploitation, but the description ('obtains an encrypted configuration file ... can recover plaintext credentials') describes an offline cryptographic recovery that in practice requires possession of the file and typically administrative access to export it - verify the realistic access path with TP-Link before treating this as remotely self-contained.

Exploit ScenarioDerived

An attacker obtains an encrypted Archer C6 V2 configuration backup or stored credential blob - for example from a leaked router backup file, a device sent for RMA/support, or a secondary network foothold. Because the same hardcoded cryptographic key is baked into every device, the attacker decrypts the file offline and recovers plaintext administrative credentials. No public exploit was identified in the provided data, but the technique requires only the universal key plus the target file.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

TP-Link Archer C6 V2 routers use a device-universal hardcoded cryptographic key to protect exported configuration backups and stored credential data, so anyone who obtains such an encrypted artifact can decrypt it and recover plaintext administrative credentials. This is a moderate-severity confidentiality issue (CVSS 4.0 base 5.9; assessed CVSS 3.1 AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N) because exploitation requires possession of the encrypted configuration file-typically after an administrative export, backup leak, support/RMA exposure, or prior compromise-rather than direct remote decryption. No public exploit has been identified at time of analysis, and TP-Link has released updated firmware for Archer C6 V2.

RemediationAI

Apply the current TP-Link firmware update for Archer C6 V2 from https://www.tp-link.com/us/support/download/archer-c6/v2/#Firmware and review TP-Link FAQ 5356 at https://www.tp-link.com/us/support/faq/5356/; the supplied data confirms the vendor has a patch but does not specify an exact fixed version string, so verify the installed build against TP-Link's release notes before considering the device remediated. Until updated, treat exported configuration backups and any protected credential data as sensitive: do not email or store them in shared locations, delete stale backups, and rotate administrative credentials after any suspected config-file exposure. Restrict router administration to trusted LANs and disable WAN-side management if it is not required; this reduces exposure but can limit remote support and management. For support or RMA returns, use a process that does not expose configuration backups, and securely wipe or retain devices according to policy.

Affected VersionsENISA

Archer C6 V2 0 <1.2.1 Build 260902

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is CWE-321 (Use of Hard-coded Cryptographic Key) in TP-Link Archer C6 V2 firmware. The device firmware relies on a static cryptographic key shared across all Archer C6 V2 units to encrypt configuration backups and other protected credential data instead of generating a unique per-device key or deriving one from device-specific secrets. That design means confidentiality depends entirely on keeping the ciphertext away from attackers: once an exported configuration file is obtained, the universal key can decrypt it offline and expose plaintext administrative credentials. The CPE cpe:2.3:a:tp-link_systems_inc.:archer_c6_v2:*:*:*:*:*:*:*:* confirms the affected model, and the assessed vector (AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N) reflects that an attacker normally needs administrative capability to generate the backup and must first acquire the encrypted artifact; it is not a direct remote code execution or unauthenticated network-decryption path.

Know when Archer C6 V2 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TPLink) PRIMARY 5.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.1 MEDIUM

Attacker must obtain the protected config file (AC:H) and normally hold admin to export it (PR:H); recovery is offline/local (AV:L) and yields credential disclosure only (C:H, I:N, A:N).

3.1 AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A hardcoded cryptographic key management vulnerability exists in Archer C6 due to the use of a universal cryptographic key shared across devices. An attacker who obtains an encrypted configuration file or other protected credential data can recover plaintext credentials.

Successful exploitation may allow unauthorized disclosure of sensitive information, including administrative credentials.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Medium
popular consumer/SOHO TP-Link router, common but not infrastructure-ubiquitous
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy