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

> A buffer overflow in Mercury IP cameras allows remote attackers to execute arbitrary commands or crash the device via PPTP configuration.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 11 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-326h-2x69-48rv

## What is CVE-2025-25526?

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

### Official description

Buffer overflow vulnerability in Mercury MIPC552W Camera v1.0 due to the lack of length verification, which is related to the configuration of the PPTP server. Attackers who successfully exploit this vulnerability can cause the remote target device to crash or execute arbitrary commands.

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

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


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

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

## Is CVE-2025-25526 being exploited?

There is no known exploitation of CVE-2025-25526 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25526 is a medium-severity memory corruption vulnerability in n/a, published on 11 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25526 in the wild and no public exploit code.

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

## Sources

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

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