CVE-2025-30240
Arbitrary File Read via Improper Symlink Handling in USB HTTPS Access Path in multiple TP-Link Aginet Devices
CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th
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.
| CWE | CWE-59 |
| Vendor | tp-link systems inc. |
| Product | hb810(us2) v1.0/1.6/2.0/2.6 |
| Published | Aug 10, 2026 |
Stay Ahead of the Next One
Get instant alerts for tp-link systems inc. hb810(us2) v1.0/1.6/2.0/2.6
Be the first to know when new unknown vulnerabilities affecting tp-link systems inc. hb810(us2) v1.0/1.6/2.0/2.6 are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
Affected Versions
TP-Link Systems Inc. / HB810(US2) V1.0/1.6/2.0/2.6
0 < 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n
TP-Link Systems Inc. / HB810(EU1) V2.0
0 < 0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n
TP-Link Systems Inc. / HB710(US2) V1.6/1.0
0 < 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
TP-Link Systems Inc. / HB710(EU1) 1.0
0 < 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
TP-Link Systems Inc. / HB610(US2) V2.6/2.0
0 < 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
TP-Link Systems Inc. / HB610(EU1)
0 < 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
TP-Link Systems Inc. / HB610(CA) V2.0
0 < 0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n
TP-Link Systems Inc. / HB410( EU1) 1.0
0 < 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n
TP-Link Systems Inc. / HB210(US2) 1.0
0 < 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
TP-Link Systems Inc. / HB210(EU1) 1.0
0 < 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
TP-Link Systems Inc. / HB210 Pro(EU1)1.0
0 < 0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n
TP-Link Systems Inc. / HB210 Pro(US2)1.0/1.6
0 < 0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n
TP-Link Systems Inc. / EB810v(EU1) V1.0
0 < 0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n
TP-Link Systems Inc. / 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
TP-Link Systems Inc. / EX220(BR) V2.0
0 < 0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n
TP-Link Systems Inc. / EX220(EU1) V1.0/1.20
0 < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. / EX220(RU) V1.0
0 < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. / EX220(US1) V1.0
0 < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. / EX222(EU1) V1.0
0 < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. / EX222(KR) V1.0
0 < 0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915
TP-Link Systems Inc. / EX222(US1) V1.0
0 < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. / EX520v(EU1)1.0
0 < 0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n
TP-Link Systems Inc. / EX820v(EU1) V1.0
0 < 0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n
TP-Link Systems Inc. / EX920(US2) V1.6/V1.0
0 < 0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n
TP-Link Systems Inc. / XC220-G3v(EU1) V2.30
0 < 1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n
TP-Link Systems Inc. / XC220-G3v(US1) V2.30
0 < 1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n
TP-Link Systems Inc. / XX530v(BR)v1.0
0 < 0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n
TP-Link Systems Inc. / XX530v(BR)v2.0
0 < 0.4.0 3.1.10 v60dc.0 Build 250520 Rel.69748n
TP-Link Systems Inc. / XX530v(US1)
0 < 0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n
TP-Link Systems Inc. / XX530v(EU1)
0 < 0.3.0 3.1.10 v6107.0 Build 250425 Rel.71973n
TP-Link Systems Inc. / VX800v(DE) V1.0
0 < 800.0.16
TP-Link Systems Inc. / VX1800v(EU1) V1.0
0 < 0.14.0 2.0.0 v6092.0 Build 250417 Rel.24761n
TP-Link Systems Inc. / VX420-G2h(AU) V3.0
0 < 0.2.0 2.0.0 v60df.0 Build 250427 Rel.38233n
Credits
Gerhard Hechenberger, Stefan Schweighofer, Constantin Schieber-Knoebl from the SEC Consult Vulnerability Lab