CVE-2026-46368: mossdef-org luci-app-https-dns-proxy · Command Injection
Affects mossdef-org luci-app-https-dns-proxySource CVE Database V5
Public exploit available (Exploit-DB) · CVSS 8.7 High.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 6.5% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 26 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
First Exploit-DB entry (opens in a new tab)
OpenWrt 23.05 - Authenticated Remote Code Execution (RCE)
, 27 days before disclosure
CVE ID reserved
by VulnCheck
, 13 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 24 minutes after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mossdef-orgluci-app-https-dns-proxy | Affected
| Fixed in– |
GitHubstangri/luci-app-https-dns-proxypkg:github/stangri/luci-app-https-dns-proxyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict access to users with luci.https-dns-proxy ACL permission and consider removing the luci-app-https-dns-proxy package if it is not required. Monitor vendor channels for updates and apply official patches once released.
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.