# CVE-2025-25662: Memory corruption in n/a

> A buffer overflow in the Tenda O4 router allows attackers to execute arbitrary code or cause a denial of service via crafted MAC filter settings.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 20 Feb 2025
- **Updated:** 21 Feb 2025
- **Also known as:** GHSA-xg8w-g5cc-8wvr

## What is CVE-2025-25662?

CVE-2025-25662 is a critical memory corruption vulnerability in n/a, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tenda O4 V3.0 V1.0.0.10(2936) is vulnerable to Buffer Overflow in the function SafeSetMacFilter of the file /goform/setMacFilterList via the argument remark/type/time.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Tenda O4 Firmware.

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

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

## Is CVE-2025-25662 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25662 is a critical memory corruption vulnerability in n/a, published on 20 Feb 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-25662 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-25662/ (Markdown: https://insights.sbomify.com/CVE-2025-25662/index.md)
```

## Sources

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

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