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

> An attacker can cause a crash or potentially execute code by sending an excessively long hostname to the Mercury MR816v2 router.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 9 Dec 2025
- **Updated:** 10 Dec 2025
- **Also known as:** GHSA-gxr6-pcf7-p63v

## What is CVE-2025-65288?

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

### Official description

A buffer overflow in the Mercury MR816v2 (081C3114 4.8.7 Build 110427 Rel 36550n) occurs when the device accepts and stores excessively long hostnames from LAN hosts without proper length validation. The affected code performs unchecked copies/concatenations into fixed-size buffers. A crafted long hostname can overflow the buffer, cause a crash (DoS) and potentially enabling remote code execution.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Mercurycom Mr816 Firmware.

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

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

## Is CVE-2025-65288 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-65289](https://insights.sbomify.com/CVE-2025-65289/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65288 is a medium-severity memory corruption vulnerability in n/a, published on 9 Dec 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-65288 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-65288/ (Markdown: https://insights.sbomify.com/CVE-2025-65288/index.md)
```

## Sources

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

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