CVE-2025-30240

Arbitrary File Read via Improper Symlink Handling in USB HTTPS Access Path in multiple TP-Link Aginet Devices

MEDIUM
5.1
CVSS Score
Published: August 10, 2026 at 10:25 PM UTC
Updated: September 29, 2026 at 11:10 AM UTC
17 products affected across 1 vendorVX800vVX1800vHB610

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
MEDIUM5.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

The affected TP-Link Aginet devices do not properly validate symbolic links created on external USB storage devices. By placing a crafted symbolic link on supported storage media, an attacker may cause the system to resolve the link. Successful exploitation may allow unauthorized read access to sensitive files within the device filesystem.

Affected

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

v < 0.14.0 2.0.0 v6092.0 Build 250417 Rel.24761n
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
v < 0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n
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
v < 0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732nv < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
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
v < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728nv < 0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915
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
v < 0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n
Affected range stops below 0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n, so it looks safe — our inference, not a vendor statement
v < 0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n
Affected range stops below 0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n, so it looks safe — our inference, not a vendor statement
v < 0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n
Affected range stops below 0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n, so it looks safe — our inference, not a vendor statement
v < 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
Affected range stops below 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n, so it looks safe — our inference, not a vendor statement
v < 0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742nv < 0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n
Affected range stops below 0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n, so it looks safe — our inference, not a vendor statement
v < 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n
Affected range stops below 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n, 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 automatablePartial impact

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

CVSS

5.1MEDIUMTPLink
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-59

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