CVE-2026-116070: dqzboy Docker-Proxy · Missing Authentication
Affects dqzboy Docker-ProxySource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 10/25/2026, 17:13:39 UTC
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wild: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dqzboyDocker-Proxy | Affected
| Fixed in– |
GitHubdqzboy/Docker-Proxypkg:github/dqzboy/Docker-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 the /api/config endpoint to trusted users or networks, and monitor for unauthorized configuration changes.
Description
Docker-Proxy versions up to 5.1.9 have a missing authentication vulnerability in the hubcmdui routes/config.js component. This flaw allows unauthenticated attackers to read and overwrite configuration data via the /api/config endpoint. Sensitive information such as the WeChat webhook URL and Telegram bot token can be exposed, and attackers can modify menuItems links, proxyDomain, and monitoring webhook destinations.
Impact
Unauthenticated attackers can read sensitive configuration data, including WeChat webhook URLs and Telegram bot tokens, potentially leading to information disclosure and unauthorized access to notification channels. They can also overwrite configuration parameters such as menuItems links, proxyDomain, and monitoring webhook destinations, which could disrupt service behavior or redirect alerts to attacker-controlled endpoints.
References
- github.com/dqzboy/Docker-Proxy/issues/109 (opens in a new tab)
- github.com/dqzboy/Docker-Proxy (opens in a new tab)
- github.com/dqzboy/Docker-Proxy/blob/4fa5a4baaeb73a9a4e317b6c7fc5db7283380136/hubcmdui/routes/config.js (opens in a new tab)
- github.com/dqzboy/Docker-Proxy/commit/a173befc5d163b1206b40298871153026fee9474 (opens in a new tab)
- vulncheck.com/advisories/docker-proxy-through-5.1.9-missing-authentication-via-hubcmdui-api-config (opens in a new tab)