# CVE-2026-18900: H3C NX15 Backend RPC esps file.exec os command injection

> Remote attackers can execute arbitrary OS commands via the file.exec RPC function in H3C NX15 devices, potentially compromising the system.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-4hjf-4f6f-fghm

## What is CVE-2026-18900?

CVE-2026-18900 is a high-severity command injection vulnerability in H3C NX15, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A weakness has been identified in H3C NX15 V100R017. This impacts the function file.exec of the file /api/esps of the component Backend RPC. This manipulation of the argument File causes os command injection. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure.

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

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


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

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

## Is CVE-2026-18900 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18900 is a high-severity command injection vulnerability in H3C NX15, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18900 exists.

Affected product: H3C NX15. 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-18900/ (Markdown: https://insights.sbomify.com/CVE-2026-18900/index.md)
```

## Sources

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

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