CVE-2026-102812: Hardcoded AES-128 Key and Fixed IV in Configuration Backup Encryption in TP-Link RE305 and Archer C7
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
A hard-coded cryptographic key vulnerability exists in the user-configuration backup mechanism of TP-Link RE305 V3 and Archer C7 V5. A fixed AES-128 key and initialization vector are embedded in the firmware configuration-management component. An attacker who obtains an affected configuration backup file may extract the cryptographic material from the firmware and use it to decrypt the backup. Successful exploitation may disclose sensitive configuration information contained in a backup file, including administrator passwords and Wi-Fi credentials.
Description quoted from the CVE record (assigned by TPLink, published 2026-10-27).
Weakness: CWE-321 Use of hard-coded cryptographic key
How it can be exploited
Exploitable with local access with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.
Live scores
- EPSS
- 0.001
low predicted chance of attack - VEDAS
- 0.052
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| TP-Link Systems Inc. RE305 v3 | before 1.1.8 Build 20260921 Rel. 42853 | Not stated |
| TP-Link Systems Inc. Archer C7 v5 | before 1.3.1 Build 20260821 Rel. 41256 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 1.1.8 Build 20260921 Rel. 42853, 1.3.1 Build 20260821 Rel. 41256.
Vendor guidance:
- https://www.tp-link.com/us/support/download/re305/v3/#Firmware (patch)
- https://www.tp-link.com/en/support/download/re305/v3/#Firmware (patch)
- https://www.tp-link.com/en/support/download/archer-c7/v5/#Firmware (patch)
- https://www.tp-link.com/us/support/download/archer-c7/v5/#Firmware (patch)
- https://www.tp-link.com/us/support/faq/5362/ (vendor-advisory)
How to detect it
This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.
Advisories on this CVE
- HKCERT reports multiple flaws in TP-Link Archer C7, C6, RE305 (full advisory)
References
Vendor advisories and patches
- https://www.tp-link.com/us/support/download/re305/v3/#Firmware (patch)
- https://www.tp-link.com/en/support/download/re305/v3/#Firmware (patch)
- https://www.tp-link.com/en/support/download/archer-c7/v5/#Firmware (patch)
- https://www.tp-link.com/us/support/download/archer-c7/v5/#Firmware (patch)
- https://www.tp-link.com/us/support/faq/5362/ (vendor-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners