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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.