# CVE-2026-69096: OpenWrt luci-app-dockerman Read ACL Remote Code Execution

> An authenticated attacker with read access can inject shell commands via the Docker plugin's RPC backend to execute arbitrary code as root.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-cq4h-h8jr-3xqv, GHSA-wjfh-jfr9-fxvm

## What is CVE-2026-69096?

CVE-2026-69096 is a high-severity command injection vulnerability in openwrt luci, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenWrt luci-app-dockerman (LuCI master and openwrt-25.12 snapshots containing the ucode docker_rpc.uc RPC backend after the JS/ucode conversion) contains an OS command injection vulnerability. The package's read ACL grants broad ubus access to docker.* / docker.container.*, which exposes the docker.container.ttyd_start method even though it performs mutating operations. The run_ttyd handler builds a shell command from the request-controlled id, cmd, and uid fields and passes it to system() without quoting or argv-style execution in the rpcd root context. An authenticated attacker holding only the luci-app-dockerman read ACL can inject shell metacharacters (e.g., in id) to execute arbitrary commands as root via an HTTP POST to /ubus. openwrt-24.10 and openwrt-23.05 do not contain this backend and are not affected; no patched version was known as of the advisory.

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

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


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

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

## Is CVE-2026-69096 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69096 is a high-severity command injection vulnerability in openwrt luci, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-69096 in the wild and no public exploit code.

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

## Sources

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

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