# CVE-2025-30239: Sensitive Data Exposure due to Hardcoded Cryptographic Keys in Multiple TP-Link Aginet Devices

> Attackers with device storage access can recover hardcoded keys to decrypt sensitive configuration data, including credentials.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-9f5f-7wxj-73g8

## What is CVE-2025-30239?

CVE-2025-30239 is a high-severity vulnerability in TP-Link Systems Inc. EB210 Pro(EU1) 1.0, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-30239?


## How do I fix CVE-2025-30239?

No fix has been published for CVE-2025-30239 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-30239 being exploited?

There is no known exploitation of CVE-2025-30239 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30239 and fix it if it is affected.

What it is: CVE-2025-30239 is a high-severity vulnerability in TP-Link Systems Inc. EB210 Pro(EU1) 1.0, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30239 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. EB210 Pro(EU1) 1.0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-30239/ (Markdown: https://insights.sbomify.com/CVE-2025-30239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30239
- OSV: https://osv.dev/vulnerability/CVE-2025-30239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-30239/
Summaries are generated and may contain mistakes; the official description above is the record.