# CVE-2025-44651: Denial of service in n/a

> An attacker can cause a denial of service on TRENDnet access points by connecting unlimited users due to a default configuration setting.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-p57m-qh59-2gqr

## What is CVE-2025-44651?

CVE-2025-44651 is a high-severity denial of service vulnerability in n/a, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In TRENDnet TPL-430AP FW1.0, the USERLIMIT_GLOBAL option is set to 0 in the bftpd-related configuration file. This can cause DoS attacks when unlimited users are connected.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Trendnet Tpl-430ap Firmware.

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

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

## Is CVE-2025-44651 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44651 is a high-severity denial of service vulnerability in n/a, published on 21 Jul 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-44651 in the wild and no public exploit code.

Affected product: n/a. 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-44651/ (Markdown: https://insights.sbomify.com/CVE-2025-44651/index.md)
```

## Sources

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

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