# CVE-2026-104474: OpenLiteSpeed before 1.9.3 Local Privilege Escalation via lsup.sh Auto-Update

> Local attackers can escalate privileges to root by replacing update packages in a writable directory, allowing arbitrary code execution during auto-update.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-4qqw-wg6j-834r

## What is CVE-2026-104474?

CVE-2026-104474 is a medium-severity vulnerability in litespeedtech openlitespeed, published on 2 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

OpenLiteSpeed before 1.9.3 contains a local privilege escalation vulnerability in admin/misc/lsup.sh that runs unverified update packages from a nobody-writable directory as root. Attackers controlling the nobody web process can replace the package in /usr/local/lsws/autoupdate/ before extraction, so its install.sh runs as root on the next update.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2026-104474 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104474 is a medium-severity vulnerability in litespeedtech openlitespeed, published on 2 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-104474 in the wild and no public exploit code.

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

## Sources

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

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