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

> A buffer overflow in the downloadFile.cgi endpoint of TOTOLINK A800R routers allows attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-qc9g-vf45-fwfp

## What is CVE-2025-28136?

CVE-2025-28136 is a medium-severity memory corruption vulnerability in n/a, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOTOLINK A800R V4.1.2cu.5137_B20200730 was found to contain a buffer overflow vulnerability in the downloadFile.cgi.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Totolink A800r Firmware.

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

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

## Is CVE-2025-28136 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28138](https://insights.sbomify.com/CVE-2025-28138/): Command injection in n/a (critical 9.8)
- [CVE-2022-25076](https://insights.sbomify.com/CVE-2022-25076/): Command injection in n/a (critical 9.8)
- [CVE-2022-36611](https://insights.sbomify.com/CVE-2022-36611/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2025-28018](https://insights.sbomify.com/CVE-2025-28018/): Memory corruption in n/a (high 7.3)
- [CVE-2025-28019](https://insights.sbomify.com/CVE-2025-28019/): Memory corruption in n/a (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28136 is a medium-severity memory corruption vulnerability in n/a, published on 15 Apr 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-28136 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-28136/ (Markdown: https://insights.sbomify.com/CVE-2025-28136/index.md)
```

## Sources

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

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