BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2025-30240High confidence

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

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

5.1MediumCVSS 4.0
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.23% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs TP-Link Systems Inc. HB810(US2) V1.0/1.6/2.0/2.6 and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-210676

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

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.

What

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.

Why

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

How

An attacker operating through physical access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

How

An attacker operating through physical access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
physical access → Improper Link Resolution Before File Access ('Link Following') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Physical
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-59 ↗

CWE-59: Improper Link Resolution Before File Access ('Link Following'). The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVPhysicalAttack vector: The attacker needs physical access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedCWE-59
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
  • HB810(US2) V1.0/1.6/2.0/2.6: < 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n
  • HB810(EU1) V2.0: < 0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n
  • HB710(US2) V1.6/1.0: < 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
  • HB710(EU1) 1.0: < 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
  • HB610(US2) V2.6/2.0: < 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
  • HB610(EU1): < 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
  • HB610(CA) V2.0: < 0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n
  • HB410( EU1) 1.0: < 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n
  • HB210(US2) 1.0: < 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
  • HB210(EU1) 1.0: < 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
  • HB210 Pro(EU1)1.0: < 0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n
  • HB210 Pro(US2)1.0/1.6: < 0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n
  • EB810v(EU1) V1.0: < 0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n
  • EX220(BR) V1.0/1.20/1.28/1.29/1.8: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
  • EX220(BR) V2.0: < 0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n
  • EX220(EU1) V1.0/1.20: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
  • EX220(RU) V1.0: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
  • EX220(US1) V1.0: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
  • EX222(EU1) V1.0: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
  • EX222(KR) V1.0: < 0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915
  • EX222(US1) V1.0: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
  • EX520v(EU1)1.0: < 0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n
  • EX820v(EU1) V1.0: < 0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n
  • EX920(US2) V1.6/V1.0: < 0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n
  • XC220-G3v(EU1) V2.30: < 1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n
  • XC220-G3v(US1) V2.30: < 1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n
  • XX530v(BR)v1.0: < 0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n
  • XX530v(BR)v2.0: < 0.4.0 3.1.10 v60dc.0 Build 250520 Rel.69748n
  • XX530v(US1): < 0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n
  • XX530v(EU1): < 0.3.0 3.1.10 v6107.0 Build 250425 Rel.71973n
  • VX800v(DE) V1.0: < 800.0.16
  • VX1800v(EU1) V1.0: < 0.14.0 2.0.0 v6092.0 Build 250417 Rel.24761n
  • VX420-G2h(AU) V3.0: < 0.2.0 2.0.0 v60df.0 Build 250427 Rel.38233n
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 12 Aug 2026, 18:18 UTC · CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-210676
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n; < 0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n; < 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n; < 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n; < 0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n; < 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    HB810(US2) V1.0/1.6/2.0/2.6: < 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n; HB810(EU1) V2.0: < 0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n; HB710(US2) V1.6/1.0: < 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n; HB710(EU1) 1.0: < 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n; HB610(US2) V2.6/2.0: < 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n; HB610(EU1): < 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n; HB610(CA) V2.0: < 0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n; HB410( EU1) 1.0: < 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n; HB210(US2) 1.0: < 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n; HB210(EU1) 1.0: < 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n; HB210 Pro(EU1)1.0: < 0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n; HB210 Pro(US2)1.0/1.6: < 0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n; EB810v(EU1) V1.0: < 0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n; EX220(BR) V1.0/1.20/1.28/1.29/1.8: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n; EX220(BR) V2.0: < 0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n; EX220(EU1) V1.0/1.20: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n; EX220(RU) V1.0: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n; EX220(US1) V1.0: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n; EX222(EU1) V1.0: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n; EX222(KR) V1.0: < 0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915; EX222(US1) V1.0: < 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n; EX520v(EU1)1.0: < 0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n; EX820v(EU1) V1.0: < 0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n; EX920(US2) V1.6/V1.0: < 0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n; XC220-G3v(EU1) V2.30: < 1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n; XC220-G3v(US1) V2.30: < 1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n; XX530v(BR)v1.0: < 0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n; XX530v(BR)v2.0: < 0.4.0 3.1.10 v60dc.0 Build 250520 Rel.69748n; XX530v(US1): < 0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n; XX530v(EU1): < 0.3.0 3.1.10 v6107.0 Build 250425 Rel.71973n; VX800v(DE) V1.0: < 800.0.16; VX1800v(EU1) V1.0: < 0.14.0 2.0.0 v6092.0 Build 250417 Rel.24761n; VX420-G2h(AU) V3.0: < 0.2.0 2.0.0 v60df.0 Build 250427 Rel.38233n · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2025-210676↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-30240 · cve.blacktree.nl