# CVE-2026-8652: Command injection in Aterm CM51FD

> An attacker with admin access can execute arbitrary OS commands on NEC Aterm routers via the web console.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 25 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-2ww7-hqm8-2qhf

## What is CVE-2026-8652?

CVE-2026-8652 is a high-severity command injection vulnerability in NEC Platforms, Ltd. Aterm CM51FD, published on 25 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An OS Command Injection vulnerability exists in Aterm. If a malicious third person gains administrator access to the product’s web console, they may be able to execute arbitrary OS commands via adjacent network.

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

## Which versions are affected by CVE-2026-8652?


## How do I fix CVE-2026-8652?

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

## Is CVE-2026-8652 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8652 and fix it if it is affected.

What it is: CVE-2026-8652 is a high-severity command injection vulnerability in NEC Platforms, Ltd. Aterm CM51FD, published on 25 May 2026. 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-2026-8652 in the wild and no public exploit code.

Affected product: NEC Platforms, Ltd. Aterm CM51FD. 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-2026-8652/ (Markdown: https://insights.sbomify.com/CVE-2026-8652/index.md)
```

## Sources

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

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