# CVE-2026-90863: Privilege Escalation via Missing Authorization in WS_FTP Manager


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-gpxj-xcv2-8mhf

## What is CVE-2026-90863?

CVE-2026-90863 is a critical vulnerability in Progress Software WS_FTP Server, published on 29 Oct 2026. 

### Official description

Missing authorization in the administrative interface of Progress Software WS_FTP Server versions prior to 2024.0.7 and 2025.0.4 on Windows could allow a delegated Host Administrator to exceed their authorized scope, potentially enabling arbitrary command execution with elevated privileges and complete compromise of the underlying server.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-90863 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90863 is a critical vulnerability in Progress Software WS_FTP Server, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-90863 in the wild and no public exploit code.

Affected product: Progress Software WS_FTP Server. 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-90863/ (Markdown: https://insights.sbomify.com/CVE-2026-90863/index.md)
```

## Sources

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

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