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

> Local attackers can exploit a stack buffer overflow in Linksys E1200 v2 router firmware to achieve arbitrary code execution or cause denial of service.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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-3crf-v4q4-gxj5

## What is CVE-2025-60692?

CVE-2025-60692 is a high-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-based buffer overflow vulnerability exists in the libshared.so library of Cisco Linksys E1200 v2 routers (Firmware E1200_v2.0.11.001_us.tar.gz). The functions get_mac_from_ip and get_ip_from_mac use sscanf with overly permissive "%100s" format specifiers to parse entries from /proc/net/arp into fixed-size buffers (v6: 50 bytes, v7 sub-arrays: 50 bytes). This allows local attackers controlling the contents of /proc/net/arp to overflow stack buffers, leading to memory corruption, denial of service, or potential arbitrary code execution.

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

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

It affects 1 product.


Products: Linksys E1200 Firmware.

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

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

## Is CVE-2025-60692 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38555](https://insights.sbomify.com/CVE-2022-38555/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-60690](https://insights.sbomify.com/CVE-2025-60690/): Memory corruption in n/a (high 8.8)
- [CVE-2025-60691](https://insights.sbomify.com/CVE-2025-60691/): Memory corruption in n/a (high 8.8)
- [CVE-2025-60694](https://insights.sbomify.com/CVE-2025-60694/): Memory corruption in n/a (high 7.5)
- [CVE-2018-3953](https://insights.sbomify.com/CVE-2018-3953/): Command injection in ESeries E1200 (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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