Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Download public TP-Link firmware image
  2. Delivery
    Reverse-engineer binary to extract hardcoded key
  3. Exploit
    Gain physical or local shell access to target device
  4. Execution
    Dump encrypted configuration partition
  5. Persist
    Decrypt configuration using extracted key
  6. Impact
    Harvest plaintext credentials and service data

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 two prerequisites: first, access to the firmware binary containing the hardcoded key (obtainable from TP-Link's public firmware download pages without authentication); second, read access to the target device's configuration storage, which requires either physical flash access (removing and reading the flash chip or using a UART/JTAG debug port), a local authenticated shell on the device, or a prior network compromise of the device that grants filesystem access. The CVSS 4.0 vector AV:A/PR:L confirms adjacent-network positioning and at least low-privilege access are required for the storage-read phase. Exploitation is limited by the requirement for either physical device access or a prior compromise; this is not a remotely unauthenticated attack. The vulnerability does not require any special device feature to be enabled - the hardcoded key is present in all affected firmware builds by default - but the attacker must still bridge the physical or network access gap to retrieve the encrypted configuration data from a specific device.

Impact

The CVSS 4.0 score of 8.5 with AV:A/PR:L reflects a meaningful but access-gated risk. The adjacent-network attack vector and requirement for storage access (physical flash read, UART shell, or prior network compromise) significantly constrain opportunistic exploitation - this is not a remotely unauthenticated attack against default configurations. However, the hardcoded-key class of vulnerability is particularly pernicious because the key is identical across the entire fleet of a given model: extracting it once breaks encryption on every deployed unit globally. TP-Link firmware images are frequently available for public download, meaning the key extraction phase may not require physical device access at all; only obtaining the specific device's encrypted configuration partition requires adjacency or physical access. No KEV listing and no public exploit code are identified, keeping real-world exploitation risk moderate rather than critical. The VC:H/VI:H impact ratings are well-founded given that decrypted configuration typically contains ISP credentials, Wi-Fi PSKs, and admin passwords. EPSS data was not provided; given no public PoC, exploit probability is likely low-to-moderate. The primary risk scenario is targeted post-compromise credential harvesting rather than mass exploitation.

Exploit ScenarioDerived

An attacker who has acquired a copy of the affected TP-Link firmware image - downloadable from the vendor's public support portal - performs static analysis to locate and extract the hardcoded symmetric key from the firmware binary. The attacker then gains physical or local shell access to a target device (for example, via a compromised home network, UART console, or direct flash-chip read), dumps the configuration partition, and applies the extracted key to decrypt it in full, recovering plaintext Wi-Fi credentials, ISP account passwords, and the device admin password. No public exploit code for this specific CVE has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Aug 10, 2026

Hardcoded cryptographic keys embedded in TP-Link Aginet firmware expose sensitive configuration data to any attacker who gains access to device storage. Affecting over 70 distinct hardware SKUs across the HB, HX, HC, EB, EC, EX, XX, XC, and VX product families, the static keys are identical across all devices sharing a firmware image, meaning key material extracted from one device - or from a publicly downloadable firmware image - decrypts configuration stores on any other device of the same model. Successful exploitation yields plaintext credentials and service configuration, and no public exploit has been identified at time of analysis. TP-Link has released patched firmware for all affected models.

RemediationAI

Apply the vendor-released firmware updates for each affected model as documented in the TP-Link security advisory at https://www.tp-link.com/us/support/faq/5239/. Each model has a specific patched firmware build (see affected products above); update via the device's web management interface or the TP-Link Deco/Tether mobile application. Because hardcoded keys are a firmware-level flaw, no runtime configuration change can fully remediate the issue - key material embedded in older firmware images remains extractable even after a device is powered off. As an interim compensating control, restrict physical and shell access to the device: disable SSH or Telnet management interfaces if not needed, limit UART/JTAG exposure, and ensure the device is not reachable from untrusted network segments where an attacker could attempt to pivot onto it. After applying the patched firmware, rotate all credentials stored in device configuration (ISP passwords, Wi-Fi PSKs, admin passwords) as a precaution, since prior firmware may have stored those credentials under the compromised key scheme. Note that credential rotation addresses potential prior exposure but does not substitute for the firmware patch.

Affected VersionsENISA

EX920(US2) V1.6/V1.0 0 <0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n
HX510(US1) V2.0 0 <0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n
EX220(US1) V1.0 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
HX510(EU1) V2.0 0 <0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n
EX222(US1) V1.0 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
HB210 Pro(EU1)1.0 0 <0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n
EX520(US1) V1.0 0 <0.7.0 3.0.0 v60b4.0 Build 251229 Rel.84306n
EX511(BR) V2.0/2.8/2.9 0 <0.9.0 3.0.0 v607e.0 Build 260520 Rel.33425n
EX141(EU1) V1.0 0 <1.7.0 3.1.0 v608a.0 Build 250418 Rel.8257n
EX521(US1) V1.0 0 <0.3.0 3.0.0 v60e3.0 Build 250925 Rel.66797n
EX511(US1) V2.0 0 <0.8.0 3.0.0 v607e.0 Build 260424 Rel.27419n
HB210 Pro(US2)1.0/1.6 0 <0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n
VX420-G2h(AU) V3.0 0 <0.2.0 2.0.0 v60df.0 Build 250427 Rel.38233n
EB210 Pro(US1) 1.0 0 <0.2.0 3.0.0 v60f4.0 Build 250807 Rel.58901n
HB610(EU1) 0 <0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
EC225-G5(US1) V1.0 0 <1.1.14.1 Build 250711 Rel.35607n(5553)
HC220-G5(US1) V1.0/1.6 0 <0.18.0 2.0.0 v605e.0 Build 250827 Rel.37904n
EC220-G5(BR) V3.0 0 <1.14.1 Build 250715 Rel.72650n(4252)
VX800v(DE) V1.0 0 <800.0.16
EX222(KR) V1.0 0 <0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915
XC220-G3v(US1) V2.30 0 <1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n
XX530v(US1) 0 <0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n
EX141(BR) V1.0/1.9 0 <1.8.0 3.1.0 v608a.0 Build 250425 Rel.40905n
EB210 Pro(EU1) 1.0 0 <0.2.0 3.0.0 v60f4.0 Build 250807 Rel.58901n
EC225-G5(BR) V1.0 0 <1.14.1 Build 250717 Rel.34953n(4252)
EB810v(EU1) V1.0 0 <0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n
XX530v(EU1) 0 <0.3.0 3.1.10 v6107.0 Build 250425 Rel.71973n
XX230v(BR) V1.0 0 <0.16.0 3.0.0 v6066.0 Build 250423 Rel.43799n
HX510(CA) V1.0/2.0 0 <0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n
HB210(EU1) 1.0 0 <0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
HC220-G5(BR) V1.30 0 <0.17.0 2.0.0 v605e.0 Build 250618 Rel.19329n
HB810(EU1) V2.0 0 <0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n
EC225-G5(EU1) V1.0 0 <1.14.1 Build 250711 Rel.35878n(4555)
HB210(US2) 1.0 0 <0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
HB610(US2) V2.6/2.0 0 <0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
EX141(US1) V1.0 0 <1.7.0 3.1.0 v608a.0 Build 250418 Rel.8257n
HB410( EU1) 1.0 0 <0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n
HX510(AU) V1.0/2.0 0 <0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n
EX220(BR) V1.0/1.20/1.28/1.29/1.8 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
EX520v(EU1)1.0 0 <0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n
EC220-G5(EU1) V3.0 0 <1.15.1 Build 260205 Rel.38208n(4555)
EX820v(EU1) V1.0 0 <0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n
XX530v(BR)v2.0 0 <0.4.0 3.1.10 v60dc.0 Build 250520 Rel.69748n
HX220(AU) V1.0 0 <0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n
XC220-G3v(EU1) V2.30 0 <1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n
EX222(EU1) V1.0 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
HX710(EU1) V1.0 0 <0.5.0 3.1.10 v6075.0 Build 260511 Rel.47847n
HX220(CA) V1.0 0 <0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n
HX510(US2) 2.6 0 <0.17.0 3.2.2 v6065.0 Build 260722 Rel.10662n
XX530v(BR)v1.0 0 <0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n
HB810(US2) V1.0/1.6/2.0/2.6 0 <0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n
HB710(EU1) 1.0 0 <0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
HB610(CA) V2.0 0 <0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n
HX710 Pro(EU1) V1.0 0 <0.4.0 3.1.10 v6082.0 Build 260204 Rel.49460n
HC220-G5(EU1) V1.20/1.0 0 <0.18.0 2.0.0 v605e.0 Build 250827 Rel.37904n
HX141(EU1) V1.0 0 <1.2.0 3.1.0 v609d.0 Build 260128 Rel.29711n
EX220(EU1) V1.0/1.20 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
HB710(US2) V1.6/1.0 0 <0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
EX220(BR) V2.0 0 <0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n
VX1800v(EU1) V1.0 0 <0.14.0 2.0.0 v6092.0 Build 250417 Rel.24761n
EX220(RU) V1.0 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
HX220(US1) V1.0/1.0 0 <0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n
HX220(EU1) V1.0 0 <0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n
EC220-G5(US1) V3.0 0 <1.14.1 Build 250715 Rel.72650n(4252)
EX511(EU1) V2.0 0 <0.9.0 3.0.0 v607e.0 Build 260520 Rel.33425n

Affected Packages

euvd vx800v_de_v1_0 fix: 800.0.16

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

CWE-321 (Use of Hard-coded Cryptographic Key) describes the root cause: the Aginet firmware ships with a symmetric or asymmetric key baked into the binary to encrypt device configuration storage. Because the key is static rather than device-unique, an adversary can perform offline firmware analysis - either by acquiring a firmware image from TP-Link's own download portal or by reading device flash - to extract the key, then apply it to decrypt any configuration partition from any device running the same firmware build. The affected CPEs span a broad range of TP-Link home-mesh and Wi-Fi extender hardware (HB810, HB710, HB610, HB410, HB210, HX510, HX710, HX220, HX141, HC220-G5, EB210 Pro, EB810v, EC220-G5, EC225-G5, EX141, EX220, EX222, EX511, EX520, EX520v, EX521, EX820v, EX920, XC220-G3v, XX530v, XX230v, VX420-G2h, VX800v, VX1800v) across US, EU, BR, CA, AU, KR, RU, and DE regional variants. The CVSS 4.0 vector AV:A reflects that the primary attack surface is adjacent-network or local device access, while PR:L indicates the attacker needs at least a foothold on the device or its storage medium.

Know when Hb810 Us2 V1 0 1 6 2 0 2 6 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 8.5 HIGH
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
vuln.today AI 7.3 HIGH

Adjacent vector and low privileges reflect that storage access requires network adjacency or local foothold; C:H and I:H reflect full credential exposure enabling subsequent config tampering.

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

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

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

Lifecycle Timeline

2
Patch available
Aug 10, 2026 - 23:04 EUVD
CVE Published
Aug 10, 2026 - 22:25 cve.org
HIGH 8.5

DescriptionCVE.org

In affected TP-Link Aginet devices, use of hardcoded cryptographic keys embedded in the firmware to protect sensitive configuration data may allow an attacker who has access to device storage to recover the keys and decrypt stored data.

Successful exploitation may allow access to decrypted sensitive configuration data, including credentials and service-related information.

Executive ViewAI

Why It Matters

Static encryption keys embedded in TP-Link Aginet firmware (70+ hardware SKUs) enable extraction of plaintext device credentials and configuration data, creating exposure of network configuration and authentication material across an organization's infrastructure. Patch availability enables remediation, but deployment urgency is high given the vulnerability's scope and the sensitivity of exposed credentials.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
High
TP-Link is a leading global consumer and SMB networking vendor with broad retail deployment.
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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 HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
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