cve.bz

CVE-2026-89052 tp-link systems inc. archer c6 v2: Use of Hard-coded Cryptographic Key

5.9 mediumEPSS 0.4%

Medium (5.9) in tp-link systems inc. archer c6 v2. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

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
EPSS
0.4% (up from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-321 Use of Hard-coded Cryptographic Key
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-89052 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89052?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89052?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-89052 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • tp-link systems inc.:archer c6 v2

Versions

From the CNA's record in the CVE List.

ProductAffected
TP-Link Systems Inc. Archer C6 V2before 1.2.1 Build 260902

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • sergioamsilva/CVE-2026-89052-archer-c6-aes Harbor Check: matches CVE 0 stars, Python, created
    PoC + Metasploit module for CVE-2026-89052: hardcoded AES credential key in TP-Link Archer C6 V2. Discovered by Sérgio Silva (CYBERS3C).

References

Check your stackJSON