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

> Local attackers can trigger stack buffer overflows in ToToLink router binaries via /proc/net/arp, causing denial of service or arbitrary code execution.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-5mqq-26vj-265q

## What is CVE-2025-60686?

CVE-2025-60686 is a medium-severity memory corruption vulnerability in n/a, published on 13 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local stack-based buffer overflow vulnerability exists in the infostat.cgi and cstecgi.cgi binaries of ToToLink routers (A720R V4.1.5cu.614_B20230630, LR1200GB V9.1.0u.6619_B20230130, and NR1800X V9.1.0u.6681_B20230703). Both programs parse the contents of /proc/net/arp using sscanf() with "%s" format specifiers into fixed-size stack buffers without length validation. Specifically, one function writes user-controlled data into a single-byte buffer, and the other into adjacent small arrays without bounds checking. An attacker who controls the contents of /proc/net/arp can trigger memory corruption, leading to denial of service or potential arbitrary code execution.

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

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

It affects 3 products.


Products: Totolink A720r Firmware, Totolink Lr1200gb Firmware, Totolink Nr1800x Firmware.

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

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

## Is CVE-2025-60686 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-23064](https://insights.sbomify.com/CVE-2023-23064/): Missing authorization in n/a (critical 9.8)
- [CVE-2021-45740](https://insights.sbomify.com/CVE-2021-45740/): Denial of service in n/a (critical 9.8)
- [CVE-2021-45742](https://insights.sbomify.com/CVE-2021-45742/): Command injection in n/a (critical 9.8)
- [CVE-2021-35324](https://insights.sbomify.com/CVE-2021-35324/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-35327](https://insights.sbomify.com/CVE-2021-35327/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60686 is a medium-severity memory corruption vulnerability in n/a, published on 13 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60686 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-60686/ (Markdown: https://insights.sbomify.com/CVE-2025-60686/index.md)
```

## Sources

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

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