CVE-2025-30239

Sensitive Data Exposure due to Hardcoded Cryptographic Keys in Multiple TP-Link Aginet Devices

HIGH
8.5
CVSS Score
Published: August 10, 2026 at 10:25 PM UTC
Updated: October 9, 2026 at 05:16 PM UTC
31 products affected across 1 vendorVX800vVX1800vVX420-G2h

Using HB810(US2) V1.0/1.6/2.0/2.6 by TP-Link Systems Inc.?

Get instant alerts when new vulnerabilities affect HB810(US2) V1.0/1.6/2.0/2.6 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

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

0
Affected range stops below 0.14.0 2.0.0 v6092.0 Build 250417 Rel.24761n, so it looks safe — our inference, not a vendor statement
0
Affected range stops below 0.2.0 3.0.0 v60f4.0 Build 250807 Rel.58901n, so it looks safe — our inference, not a vendor statement
0
Affected range stops below 0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n, so it looks safe — our inference, not a vendor statement
0
Affected range stops below 1.14.1 Build 250715 Rel.72650n(4252), so it looks safe — our inference, not a vendor statement
Affected range stops below 1.15.1 Build 260205 Rel.38208n(4555), so it looks safe — our inference, not a vendor statement
0
Affected range stops below 1.1.14.1 Build 250711 Rel.35607n(5553), so it looks safe — our inference, not a vendor statement
Affected range stops below 1.14.1 Build 250711 Rel.35878n(4555), so it looks safe — our inference, not a vendor statement
Affected range stops below 1.14.1 Build 250717 Rel.34953n(4252), so it looks safe — our inference, not a vendor statement
0
Affected range stops below 1.7.0 3.1.0 v608a.0 Build 250418 Rel.8257n, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.8.0 3.1.0 v608a.0 Build 250425 Rel.40905n, so it looks safe — our inference, not a vendor statement
0
Affected range stops below 0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n, so it looks safe — our inference, not a vendor statement
0
Affected range stops below 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915, so it looks safe — our inference, not a vendor statement
0
Affected range stops below 0.8.0 3.0.0 v607e.0 Build 260424 Rel.27419n, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.9.0 3.0.0 v607e.0 Build 260520 Rel.33425n, so it looks safe — our inference, not a vendor statement
0
Affected range stops below 0.7.0 3.0.0 v60b4.0 Build 251229 Rel.84306n, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

Vendor Advisory
Source: cverecord
https://www.tp-link.com/us/support/faq/5239/

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

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

CVSS

8.5HIGHTPLink
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-321

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