# CVE-2026-1791: Arbitrary File Upload Vulnerability in Operation and Maintenance Security Gateway

> Attackers can upload malicious web shells to the Hillstone Operation and Maintenance Security Gateway, leading to remote code execution.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-w3f6-336f-pxmh

## What is CVE-2026-1791?

CVE-2026-1791 is a low-severity vulnerability in Hillstone Networks Operation and Maintenance Security Gateway, published on 4 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in Hillstone Networks Operation and Maintenance Security Gateway on Linux allows Upload a Web Shell to a Web Server.This issue affects Operation and Maintenance Security Gateway: V5.5ST00001B113.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-1791 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1791 is a low-severity vulnerability in Hillstone Networks Operation and Maintenance Security Gateway, published on 4 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1791 in the wild and no public exploit code.

Affected product: Hillstone Networks Operation and Maintenance Security Gateway. 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-1791/ (Markdown: https://insights.sbomify.com/CVE-2026-1791/index.md)
```

## Sources

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

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