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

> A stack buffer overflow in the D-Link DIR-816A2 router firmware allows arbitrary code execution if an attacker controls the /proc/version content.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Nov 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-xhj4-39f6-qqcq

## What is CVE-2025-60679?

CVE-2025-60679 is a high-severity memory corruption vulnerability in Dlink Dir-816 Firmware, published on 13 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A stack buffer overflow vulnerability exists in the D-Link DIR-816A2 router firmware DIR-816A2_FWv1.10CNB05_R1B011D88210.img in the upload.cgi module, which handles firmware version information. The vulnerability occurs because /proc/version is read into a 512-byte buffer and then concatenated using sprintf() into another 512-byte buffer containing a 29-byte constant. Input exceeding 481 bytes triggers a stack buffer overflow, allowing an attacker who can control /proc/version content to potentially execute arbitrary code on the device.

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

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

It affects 1 product.


Products: Dlink Dir-816 Firmware.

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

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

## Is CVE-2025-60679 being exploited?

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

## Other vulnerabilities in Dlink Dir-816 Firmware

- [CVE-2025-45931](https://insights.sbomify.com/CVE-2025-45931/): Command injection in n/a (critical 9.8)
- [CVE-2024-57684](https://insights.sbomify.com/CVE-2024-57684/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-24331](https://insights.sbomify.com/CVE-2023-24331/): Command injection in n/a (critical 9.8)
- [CVE-2024-24321](https://insights.sbomify.com/CVE-2024-24321/): Command injection in n/a (critical 9.8)
- [CVE-2023-39637](https://insights.sbomify.com/CVE-2023-39637/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60679 is a high-severity memory corruption vulnerability in Dlink Dir-816 Firmware, published on 13 Nov 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-60679 exists.

Affected product: Dlink Dir-816 Firmware. 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-60679/ (Markdown: https://insights.sbomify.com/CVE-2025-60679/index.md)
```

## Sources

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

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