# CVE-2025-8890: Authenticated RCE in SDMC NE6037 router

> Authenticated attackers can execute arbitrary commands via the network diagnostics tool in SDMC NE6037 routers.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2025
- **Updated:** 18 Mar 2026
- **Also known as:** GHSA-x463-6cxf-7g5h

## What is CVE-2025-8890?

CVE-2025-8890 is a critical command injection vulnerability in SDMC NE6037, published on 27 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Firmware in SDMC NE6037 routers prior to version 7.1.12.2.44 has a network diagnostics tool vulnerable to a shell command injection attacks.
In order to exploit this vulnerability, an attacker has to log in to the router's administrative portal, which by default is reachable only via LAN ports.

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

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


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

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

## Is CVE-2025-8890 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8890 is a critical command injection vulnerability in SDMC NE6037, published on 27 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-8890 exists.

Affected product: SDMC NE6037. 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-8890/ (Markdown: https://insights.sbomify.com/CVE-2025-8890/index.md)
```

## Sources

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

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