Skip to main content
Mallory
HighVulnerability

CVE-2026-69096: OS Command Injection in OpenWrt luci-app-dockerman

Published Aug 3, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.7High · v4
EPSS3.3%89th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-69096CWE-78 · Improper Neutralization of Special…

CVE-2026-69096 is an OS command injection vulnerability in OpenWrt LuCI's luci-app-dockerman component, affecting LuCI master and OpenWrt 25.12 snapshots that include the ucode-based docker_rpc.uc RPC backend introduced after the JS-to-ucode conversion. The flaw arises from two conditions: the package's read ACL grants broad ubus access to docker.* and docker.container.*, exposing the docker.container.ttyd_start method despite its mutating behavior; and the run_ttyd handler constructs a shell command from request-controlled id, cmd, and uid parameters and passes that command to system() without safe quoting or argv-style execution. Because the command is executed in the rpcd root context, an authenticated user with only the luci-app-dockerman read ACL can inject shell metacharacters through those fields and achieve arbitrary command execution as root via the ubus HTTP interface. OpenWrt 24.10 and 23.05 are not affected because they do not include the vulnerable backend.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in authenticated remote arbitrary command execution with root privileges on the affected device. This enables full compromise of confidentiality, integrity, and availability, including reading or modifying system and container data, altering device configuration, installing persistent payloads, pivoting to other systems reachable from the device, and disrupting services or rendering the device unstable or unusable.

Mitigation

If you can’t patch tonight, do this now.

Until a patch is available, remove or disable luci-app-dockerman or the vulnerable docker_rpc.uc backend where operationally feasible. Restrict access to the ubus HTTP interface to trusted administrators only, and remove or tightly limit the luci-app-dockerman read ACL for non-administrative users. Where possible, segment management access, require strong authentication for LuCI and ubus-exposed services, and monitor for unexpected use of docker-related ubus methods from low-privilege accounts.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed release once one is available. A proper fix should remove the unsafe shell construction in the run_ttyd handler by avoiding system()-based command execution with untrusted input, using argv-style execution or equivalent safe process invocation, and enforcing strict validation of user-supplied parameters. The exposed ubus permissions should also be corrected so that mutating methods such as docker.container.ttyd_start are not reachable through overly broad read ACLs. If maintaining a custom build, backport the upstream fix for the docker_rpc.uc backend and the associated ACL changes.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-69096 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-69096 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-69096?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-69096.
Is there a patch for CVE-2026-69096?
Upgrade to a vendor-fixed release once one is available. A proper fix should remove the unsafe shell construction in the run_ttyd handler by avoiding system()-based command execution with untrusted input, using argv-style execution or equivalent safe process invocation, and enforcing strict validation of user-supplied parameters.
How severe is CVE-2026-69096?
CVE-2026-69096 has a CVSS v4 score of 8.7 (High) and an EPSS score of 3.3% (89th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.