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

> Attackers can cause a Denial of Service on TP-Link TL-WR841ND V11 routers by sending crafted packets to the WAN IPv6 configuration page.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-wp6r-c52j-pjff

## What is CVE-2025-25899?

CVE-2025-25899 is a low-severity denial of service vulnerability in n/a, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11 via the 'gw' parameter at /userRpm/WanDynamicIpV6CfgRpm.htm. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted packet.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Tp-Link Tl-Wr841nd V11 Firmware.

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

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

## Is CVE-2025-25899 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25899 exists.

## Other vulnerabilities in n/a

- [CVE-2025-25900](https://insights.sbomify.com/CVE-2025-25900/): Memory corruption in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25899 is a low-severity denial of service vulnerability in n/a, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25899 exists.

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-25899/ (Markdown: https://insights.sbomify.com/CVE-2025-25899/index.md)
```

## Sources

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

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