CVE-2025-30240

Arbitrary file read via crafted USB symlink

Published Aug 10, 2026 · Updated Aug 10, 2026

Link following in TP-Link Aginet device firmware allows physically proximate attackers to read sensitive device files through USB media. The USB HTTPS access path resolves a crafted symbolic link on external storage without verifying that its target remains on that storage. Physical access to place the media is required; successful exploitation exposes readable files from the device filesystem without altering them.

CVSS severity5.1
Medium
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Link following in TP-Link Aginet device firmware allows physically proximate attackers to read sensitive device files through USB media. The USB HTTPS access path resolves a crafted symbolic link on external storage without verifying that its target remains on that storage. Physical access to place the media is required; successful exploitation exposes readable files from the device filesystem without altering them.

The record

CVE
CVE-2025-30240
Published
Aug 10, 2026
Updated
Aug 10, 2026
Vendor
TP-Link Systems Inc.
Product
EX820v(EU1)
Classifications
CWE-59, CAPEC-132, T1005
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

TP-Link Systems Inc. · EX820v(EU1)version=0 <0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n
TP-Link Systems Inc. · HB610(CA)version=0 <0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n
TP-Link Systems Inc. · EX222(US1)version=0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. · XX530v(EU1)version=0 <0.3.0 3.1.10 v6107.0 Build 250425 Rel.71973n
TP-Link Systems Inc. · VX800v(DE)version=0 <800.0.16
TP-Link Systems Inc. · HB610(US2)version=0 <0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
TP-Link Systems Inc. · HB810(EU1)version=0 <0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n
TP-Link Systems Inc. · HB210 Pro(US2)version=0 <0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n
TP-Link Systems Inc. · EB810v(EU1)version=0 <0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n
TP-Link Systems Inc. · EX222(EU1)version=0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. · EX520v(EU1)version=0 <0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n
TP-Link Systems Inc. · HB210(EU1)version=0 <0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
TP-Link Systems Inc. · EX920(US2)version=0 <0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n
TP-Link Systems Inc. · EX222(KR)version=0 <0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915
TP-Link Systems Inc. · XX530v(BR)version=0 <0.4.0 3.1.10 v60dc.0 Build 250520 Rel.69748n; version=0 <0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n
TP-Link Systems Inc. · HB710(US2)version=0 <0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
TP-Link Systems Inc. · HB410(EU1)version=0 <0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n
TP-Link Systems Inc. · HB610(EU1)version=0 <0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
TP-Link Systems Inc. · EX220(RU)version=0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. · HB210 Pro(EU1)version=0 <0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n
TP-Link Systems Inc. · XC220-G3vversion=0 <1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n
TP-Link Systems Inc. · Archer VX1800vversion=0 <0.14.0 2.0.0 v6092.0 Build 250417 Rel.24761n
TP-Link Systems Inc. · EX220(EU1)version=0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. · EX220(BR)version=0 <0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n; version=0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. · EX220(US1)version=0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
TP-Link Systems Inc. · XX530v(US1)version=0 <0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n
TP-Link Systems Inc. · HB710(EU1)version=0 <0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
TP-Link Systems Inc. · HB210(US2)version=0 <0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
TP-Link Systems Inc. · HB810(US2)version=0 <0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n
TP-Link Systems Inc. · VX420-G2hversion=0 <0.2.0 2.0.0 v60df.0 Build 250427 Rel.38233n

Published CVSS scores

5.1TP-Link Systems Inc.CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-59Improper Link Resolution Before File Access ('Link Following')
CAPEC-132Symlink Attack
T1005Data from Local System

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo