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

> A stack buffer overflow in ToToLink router firmware allows arbitrary code execution if an attacker can modify the /proc/stat file.

- **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-273x-ghvh-vxh2

## What is CVE-2025-60685?

CVE-2025-60685 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 stack buffer overflow exists in the ToToLink A720R Router firmware V4.1.5cu.614_B20230630 within the sysconf binary (sub_401EE0 function). The binary reads the /proc/stat file using fgets() into a local buffer and subsequently parses the line using sscanf() into a single-byte variable with the %s format specifier. Maliciously crafted /proc/stat content can overwrite adjacent stack memory, potentially allowing an attacker with filesystem write privileges to execute arbitrary code on the device.

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

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

It affects 1 product.


Products: Totolink A720r Firmware.

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

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

## Is CVE-2025-60685 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60685 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-60685 and fix it if it is affected.

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

## Sources

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

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