# CVE-2026-88738: File upload in n/a

> An attacker with admin privileges can upload a malicious executable to the webUI, leading to remote code execution via direct HTTP access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-64j7-pv8p-xprg

## What is CVE-2026-88738?

CVE-2026-88738 is a high-severity vulnerability in n/a, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jazzware RT1000 Edge webUI v. 20.0.1 contains an unrestricted file upload vulnerability in the upgrade package upload functionality. An attacker with administrative privileges can upload a server-side executable file. The uploaded file is stored in a web-accessible executable location and can be accessed directly over HTTP without authentication, resulting in remote code execution.

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

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


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

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

## Is CVE-2026-88738 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88738 is a high-severity vulnerability in n/a, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88738 exists.

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-2026-88738/ (Markdown: https://insights.sbomify.com/CVE-2026-88738/index.md)
```

## Sources

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

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