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

> A stack buffer overflow in D-Link router firmware allows arbitrary code execution via a malicious USB device, requiring physical access.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** 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-j478-r957-h872

## What is CVE-2025-60674?

CVE-2025-60674 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 vulnerability exists in the D-Link DIR-878A1 router firmware FW101B04.bin in the rc binary's USB storage handling module. The vulnerability occurs when the "Serial Number" field from a USB device is read via sscanf into a 64-byte stack buffer, while fgets reads up to 127 bytes, causing a stack overflow. An attacker with physical access or control over a USB device can exploit this vulnerability to potentially execute arbitrary code on the device.

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

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

It affects 1 product.


Products: Dlink Dir-878 Firmware.

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

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

## Is CVE-2025-60674 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-27720](https://insights.sbomify.com/CVE-2023-27720/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-24798](https://insights.sbomify.com/CVE-2023-24798/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-24799](https://insights.sbomify.com/CVE-2023-24799/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-24800](https://insights.sbomify.com/CVE-2023-24800/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-44202](https://insights.sbomify.com/CVE-2022-44202/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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