# CVE-2025-65882: Command injection in n/a

> Attackers can execute arbitrary commands or write files in OpenMPTCProuter due to improper neutralization of special elements used in an OS command.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-q62x-rch6-pwxf

## What is CVE-2025-65882?

CVE-2025-65882 is a critical command injection vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in openmptcprouter thru 0.64 in file common/package/utils/sys-upgrade-helper/src/tools/sysupgrade.c in function create_xor_ipad_opad allowing attackers to potentially write arbitrary files or execute arbitrary commands.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Openmptcprouter Openmptcprouter.

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

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

## Is CVE-2025-65882 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-31245](https://insights.sbomify.com/CVE-2021-31245/): Auth bypass in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65882 is a critical command injection vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65882 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-65882/ (Markdown: https://insights.sbomify.com/CVE-2025-65882/index.md)
```

## Sources

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

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