# CVE-2025-8759: TRENDnet TN-200 Lighttpd hard-coded key

> A hard-coded cryptographic key in the Lighttpd component of TRENDnet TN-200 devices allows remote attackers to bypass security controls.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2025
- **Updated:** 12 Aug 2025
- **Also known as:** GHSA-v837-44qq-4rg5

## What is CVE-2025-8759?

CVE-2025-8759 is a medium-severity vulnerability in TRENDnet TN-200, published on 9 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in TRENDnet TN-200 1.02b02. It has been declared as problematic. This vulnerability affects unknown code of the component Lighttpd. The manipulation of the argument secdownload.secret with the input neV3rUseMe leads to use of hard-coded cryptographic key
 . The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

It affects 1 product.


Products: Trendnet Tn-200 Firmware.

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

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

## Is CVE-2025-8759 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8759 is a medium-severity vulnerability in TRENDnet TN-200, published on 9 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8759 in the wild and no public exploit code.

Affected product: TRENDnet TN-200. 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-8759/ (Markdown: https://insights.sbomify.com/CVE-2025-8759/index.md)
```

## Sources

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

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