CVE-2026-46368
Description
luci-app-https-dns-proxy through 2025.12.29-5 — an optional LuCI web UI add-on for the https-dns-proxy package, distributed through the OpenWrt community packages feed and not installed by default — contains a command injection vulnerability in the setInitAction function. An authenticated user holding the luci.https-dns-proxy ACL permission can inject shell metacharacters through the 'name' parameter of a ubus RPC call to luci.https-dns-proxy setInitAction, resulting in arbitrary command execution as root on the underlying device. Core OpenWrt is not affected; only installations that have opted in to the luci-app-https-dns-proxy package are vulnerable.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Command injection in luci-app-https-dns-proxy allows authenticated users with specific ACL to execute arbitrary commands as root on OpenWrt devices.
Vulnerability
A command injection vulnerability exists in the setInitAction function of luci-app-https-dns-proxy through version 2025.12.29-5. This optional LuCI web UI add-on for the https-dns-proxy package is distributed via the OpenWrt community packages feed and is not installed by default. The flaw allows an authenticated user holding the luci.https-dns-proxy ACL permission to inject shell metacharacters through the name parameter of a ubus RPC call to luci.https-dns-proxy setInitAction. Core OpenWrt installations are unaffected; only systems with the luci-app-https-dns-proxy package installed are vulnerable [1][3].
Exploitation
An attacker must have a valid user account on the OpenWrt device with the luci.https-dns-proxy ACL permission. No additional user interaction is required beyond authentication. The attacker sends a crafted ubus RPC call to the setInitAction method, embedding shell metacharacters (e.g., ;, |, ` `) in the name` parameter. This payload is then executed by the underlying shell with root privileges. The exploit can be performed remotely if the LuCI web interface is exposed over the network [1][3].
Impact
Successful exploitation results in arbitrary command execution as the root user, leading to full compromise of the OpenWrt device. The attacker can install persistent backdoors, exfiltrate data, or pivot to other network hosts. The confidentiality, integrity, and availability of the device are completely undermined [1][3].
Mitigation
As of the publication date, no patched version of luci-app-https-dns-proxy has been released. The vulnerability affects all versions through 2025.12.29-5. Users are advised to remove the luci-app-https-dns-proxy package if not required, or restrict the luci.https-dns-proxy ACL permission to trusted administrators only. The vulnerability is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog [1][3].
AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2(expand)+ 1 more
- (no CPE)
- (no CPE)range: <=2025.12.29-5
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.